At 08:52 AM 4/10/2011 +1000, Ben Finney wrote:
This is an often-overlooked case, I think. The unspoken assumption is
often that ``setup.py`` is a suitable place for the overall version
string, but this is not the case when that string must be read by
non-Python programs.
If you haven't used the
Earlier this year there was some discussion[0] about putting up a page
on the wiki where developers could list the feature proposals they
most wanted and most hated for the benefit of those posting to
python-ideas. It's taken me a while to get around to it, but I've put
up a skeleton for the page a
Howdy Barry,
Nitpick: Please call these “version strings”. A version string is hardly
ever just one number, and not in the general case anyway.
I'd like to suggest another user story:
Barry Warsaw writes:
> User Stories
>
Emily maintains a package consisting of programs and
On 4/9/2011 9:23 AM, Éric Araujo wrote:
Hi,
Le 06/04/2011 23:58, Glenn Linderman a écrit :
On 4/6/2011 7:26 AM, Nick Coghlan wrote:
On Wed, Apr 6, 2011 at 6:22 AM, Glenn
Linderman wrote:
With more standardization of versions, should the version module be
promoted
to stdlib directly?
When T
Hi,
Le 07/04/2011 13:10, Michael Foord a écrit :
On 4/5/2011 11:52 AM, Barry Warsaw wrote:
__version__ =
pkgutil.get_distribution('elle').metadata['version']
I really dislike this way of specifying the version. For a start it
is
really ugly.
More importantly it means the version informa
Hi,
Le 06/04/2011 23:58, Glenn Linderman a écrit :
On 4/6/2011 7:26 AM, Nick Coghlan wrote:
On Wed, Apr 6, 2011 at 6:22 AM, Glenn
Linderman wrote:
With more standardization of versions, should the version module be
promoted
to stdlib directly?
When Tarek lands "packaging" (i.e. what distuti
