Jan
14
awarded Yearling
Jan
14
awarded Yearling
Sep
27
comment How do I write a setup.py for a twistd/twisted plugin that works with setuptools, distribute, etc?
With the fix to Pip bug #355, Chris Miles's approach seems to work. I used it to package oauth-proxy just now and it appeared to work: github.com/mojodna/oauth-proxy/pull/5
Aug
31
awarded Yearling
Jul
13
awarded Yearling
Jul
13
awarded Yearling
Apr
29
awarded Necromancer
Apr
20
awarded Supporter
Apr
12
awarded Good Answer
Mar
14
comment Standard way to embed version into python package?
Here's a mostly-complementary tool by my long-time programming partner Brian Warner: blog.mozilla.org/warner/2012/01/31/… Versioneer is a tool to generate the version number from git history. Ideally I would like to use Versioneer to generate the version number, and then use the technique described in my answer here to make that version number available to all the places where it is needed. I'm doing something like that in this project: github.com/zooko/pycryptopp
Mar
14
revised Standard way to embed version into python package?
deleted 24 characters in body
Feb
5
awarded Nice Answer
Oct
23
awarded Supporter
Mar
7
awarded Announcer
Mar
1
awarded Scholar
Mar
1
accepted How can I change the background colors of a table cell in reStructuredText?
Feb
21
comment Standard way to embed version into python package?
Jonathan Hartley: I agree it would be slightly simpler for your "setup.py" to write the "version.py" file instead of parsing it, but it would open up a window for inconsistency, when you've edited your setup.py to have the new version but haven't yet executed setup.py to update the version.py file. Another reason to have the canonical version be in a small separate file is that it makes it easy for other tools, such as tools that read your revision control state, to write the version file.
Feb
12
awarded Nice Answer
Feb
8
awarded Critic
Jan
30
awarded Supporter
1 2 3 4 5