On Jun 28, 2006, at 11:28 PM, Phillip J. Eby wrote
...
It isn't my intention to provide daily builds. I just happen wanted
to make
quick and dirty releases while stuff is new. These are like alpha
release, but I'm
leveraging the revision tagging to automate generation of release
numbers.
At 06:19 AM 6/29/2006 -0400, Jim Fulton wrote:
1. If I'm going to edit setup.cfg, I might as well edit setup.py
Note that you needn't edit anything if you use the --tag-build option, e.g.:
python setup.py egg_info --tag-build=snap3 register sdist bdist_egg upload
Assuming that setup.cfg
If I do something like:
python2.4 setup.py register bdist_egg upload
as recommended in the setuptools documentation, I end up with 2
releases in PyPi. One has all my descriptive information and the
other has the egg. One or more will or won't be hidden according
some rule that I
At 05:16 PM 6/28/2006 -0400, Jim Fulton wrote:
Interesting. I thought that --tag-svn-revision was a common/recommended
practice.
It *is* -- but not for releases being sent to PyPI. a dev-r release is
a development snapshot rather than an official release.
I followed the advice to have
On Jun 28, 2006, at 5:30 PM, Phillip J. Eby wrote:
At 05:16 PM 6/28/2006 -0400, Jim Fulton wrote:
Interesting. I thought that --tag-svn-revision was a common/
recommended
practice.
It *is* -- but not for releases being sent to PyPI. a dev-r
release is a development snapshot
At 05:42 PM 6/28/2006 -0400, Jim Fulton wrote:
If I want people to be able to download it, I have to upload it
somewhere.
Not necessarily. If you have a pure-Python package, and your target
audience has Subversion, you can provide a URL on PyPI that always obtains
the most recent possible
On Jun 28, 2006, at 6:09 PM, Phillip J. Eby wrote:
At 05:42 PM 6/28/2006 -0400, Jim Fulton wrote:
If I want people to be able to download it, I have to upload it
somewhere.
Not necessarily. If you have a pure-Python package, and your
target audience has Subversion, you can provide a URL
