746 karma · joined January 29, 2013
I never really understood the "rather stay with py2.7" thing. I get it with big old monolithic applications. You don't "just" rewrite those, but _every new python project_ should be done with the latest stable release.
Is anyone starting their PHP projects on PHP4? Any new node projects in 0.10? Of course not, that would be moronic.
I never use guest networks for that exact reason. I know that my traffic and my connection is my own, and works. Way easier imo.
I know i have a few naming clashes, but i havn't been able to come up with a better one. Suggestions welcome.
Also, i did a blog post on this tool http://www.tudb.org/articles/2014/03/31/vpython/
We take different aproaches though.
Repo link for reference: https://github.com/tbug/vpython
Mine expects you to know virtualenv and how it works, and also that you explicitly install it. Same goes for dependencies.
My needs where to avoid sourcing the virtualenv, so i wrote the tool to fix just that. Also, i built mine to resolve symlinks and be usable as the shebang in your python scripts, which is pretty neat when writing command line tools.
Most of my projects are long running though (webservers, number crunchers, etc), so the extra miliseconds it takes to load is really not that important.
I currently use http://tudb.org/articles/2014/03/31/vpython/ for pretty much all of my python projects (also, i am the author of vpython).
And if possible, store the session information somewhere else than your database. Redis and Memcached is a nice fit for stuff like that.
I still prefer docopt (https://github.com/docopt/docopt) . It is so much simpler to use. Click seems to be a bit overengineered.
If we need to follow that logic (to include useful non-primitives) we would end up with a clusterfuck of a spec that noone would want to implement.
Maybe the question is instead; why the hell do we need comments (and loosening of t he syntax, etc) in the first place?
Are we seriously going to keep insisting on json as a configuration format?
As Stormbrew already pointed out, we already have a format that is ideal for configurations (and sure, data exchange, why not), and it is called yaml.
yaml have comments
yaml makes it easy to enter multiline strings
and most if all; yaml is very very easy to write!
tl;dr: Just use a format suited for your needs instead of trying to change something that doesn't. Oh, and a couple of smiley faces thrown in there to ensure people don't read this in the wrong tone. People do that.. Like, all the time.. damn, now my tl;dr is too damn long! i have to add another.
tl;dr;tl;dr YAML BITCHES! (╯°□°)╯︵ ┻━┻ (but also, a puppy: http://i.imgur.com/kuDsS0i.jpg )