434 karma · joined April 6, 2009
Basically my pythonstartup.py contains the extra check for os:
AP_AUTOCOMPLETE=False
import sys
try:
import readline
except ImportError:
print "Module readline unavailable"
else:
import rlcompleter
readline.parse_and_bind("tab: complete")
if sys.platform == 'darwin':
readline.parse_and_bind("bind ^I rl_complete")
AP_AUTOCOMPLETE=TrueAs for this second part, "once it's published it should always remain out there", I'm not very sure it's a good idea. In many cases I'd actually like to be able to say that a piece of content has expired (the content is not relevant anymore).
1. Your boss says something vague
2. You think very hard on how to move the needle
3. Where’s the data?
4. What’s in this dataset?
5. What’s all the f#$#$ crap in the data?
6. Clean the data
7. Run some off-the-shelf data mining algorithm
8. ...
9. Productionize, act on the insight
10. Rinse, repeat
[1] http://www.slideshare.net/Hadoop_Summit/scaling-big-data-min...
Even if we like it or not, the rent is ridiculously expensive.
(someone new to SF that will probably never get used to the peeing in the streets)
Where there the IBM, Apple 2, Das keyboard fans?
In the early days, it always took me a lot more time to get from finding an answer to using that answer in my code. The main reason is that I didn't want to just copy paste something without understanding it. On the other hand, a more experienced colleague of mine was sifting through books and forums and pushing code a lot faster. I talked to him trying to understand what I'm doing wrong. As I've learned (actually both of us learned), the only difference was the existing knowledge each of us had about the environment and the app. Over time I got to be a lot faster at finding an answer and moving along, but that came only with becoming more familiar with the tools/lang/etc and being able to understand things faster.
alex @ rethinkdb
On the other hand, I've seen it in the movies that they can disappear... I assume that's what they do before someone can actually try to run their code.
I spend most of my time on my computer programming (or at least I did this until very recently).
What I've noticed in the last 2 years is that except maybe the Xcode environment, Apple has started to ignore every other dev environments. People have been working a lot on keeping things going (Fink, MacPort, homebrew), but by the day my feeling is that Apple doesn't care at all about this.
Basically the target audience shifted from geeks to mass audience (click to buy this app, watch a movie on this great display, etc.) and AppStore developers. Business-wise it's clear they can ignore the small segment of developers. Karma-wise I'm not convinced that's wise.
1. Using PGBouncer seems to be the ideal solution, but I'm not sure other databases actually provide a proxy. I haven't heard of something like this for MySQL (a) I might be wrong, please provide a link, b) I'm know some will say "just don't use MySQL")
This aside, I would expect a connection pool implementation to support at least the following:
1. min: minimum number of connections
2. max: maximum number of connections
3. idleTime: time interval after which idle connections are automatically closed
4. connection cleanup (most often done when returned to the pool). Basically making sure that the connection object is pristine
If it doesn't do all these, then it's probably not something you'd want to use.
The main reason I'm saying this is that I feel that the open source world is not an infinite dump area where everyone just throws out code of any quality (in many cases just for having something to add on the 2nd page of a résumé).
This is not to say that authors are required to implement additional features or support a piece of code forever. But trying to deliver as much as the original "promise" of the project and making it clear what's the status of the project is the responsibility of the author. Browse GitHub and tell me how many projects are marked as "defunct" or "abandoned" or "unmaintained". (maybe Github should automatically do this...)
I've started by asking people heavily involved in the Python world. Statistically irrelevant, but the majority of answers I've got back were:
1. production systems: 2.7.x
2. old maintenance mode: 2.6
3. some 3.x
I've also tried asking the PSF, hoping that they might have more data. They pointed out to the download page:
> "The current production versions are Python 2.7.3 and Python 3.3.0"
A statistically relevant survey would need to take in consideration:
1. what major Linux distributions include as the default Python version
2. what versions hosting providers support by default
3. the percentage of Python libraries that work with Python 2.7 and Python 3.3
A lot of effort would be needed to pull together all these details, but I think the Python community would benefit from having this data around (even if some might find this detrimental to the advance of Python)
As a side note, each programming language has its own idioms. We tried to bring the ReQL query to each language in a way that felt as close as possible to the host PL (as opposed to say SQL which you need to use it as it is; and that led to the hundreds or thousands of wrapper libraries/ORMs. etc).
alex @ rethinkdb
thanks,
alex @ rethinkdb
In a way queries are lazy. You can write a query and without calling `run` on it nothing happens. The whole chained ops are executed at once when `run` is called.
> That said, it is also my opinion that the ORM syntax needs a bit of love, for all the reasons stated above.
This is not an "ORM" per se. It's a query API or data manipulation language. The next version will bring a few improvements to it.