argparse-1.0.1 does not install about argparse HOT 9 CLOSED

Apologies. Please give it another try!

Hi Steven,

Did you release a new version (1.0.2), or simply replaced the old tarball with 
the 
new one of the same name?

If you did the later, then users won't be able to "upgrade" to the newer 
version. 
Even though the distutils may not have versioned upgrades, tools like PyPM (to 
be 
released by beginning of October this year) will not be able to use the new 
tarball 
released under the same name. See 
http://pypm.activestate.com/list-a.html#argparse 

It is for this reason, one better not "edit" already released tarballs.

I just replaced the .zip file with the assumption that only a small number of 
people
had downloaded it already, and no one on Unix had successfully installed it. ;-)

I'm not totally sure what "upgrade" means as far as PyPM goes (which I know 
nothing
about), but can you really "upgrade" a package that never installed in the 
first place? 

Note that the bug was only in the setup.py, not in the actual module. If anyone
successfully installed the package, then they definitely have no need of the 
updated
.zip file - the argparse.py file is identical in both.

Hi Steven,

[srid]
> users won't be able to "upgrade" to the newer version. 

[steven]
>> but can you really "upgrade" a package that never 
>> installed in the first place

Nope. Nevermind about it then.

> I'm not totally sure what "upgrade" means as far as 
> PyPM goes (which I know nothing about)

PyPM is ActiveState's upcoming Python package manager similar to PPM or 
Debian's 
apt. Basically, "argparse 1.0.1" build failed on Linux, Mac and thus is 
automatically marked as "do not try to build again [the same tarball]". A new 
build 
happens only when a new release (i.e., newer version) comes (or we have to 
remember 
to manually rebuild the package).

As a result of the editing done in 1.0.1 and PyPM's build-behavior illustrated 
above, argparse 1.0.1 remains unavailable in the PyPM repository. I can 
manually 
trigger a rebuild of argparse now, but this cannot be practically done for each 
and 
every project "editing" their releases. 

I gather you're monitoring PyPI somehow to determine when new releases are 
made? Is
it possible to also monitor when new files are uploaded? At least in the case 
where
only the build (e.g. setup.py) is broken, it really doesn't seem inappropriate 
to
call it the same release.

That said, I don't plan to make a habit of "editing" releases. ;-)

> I gather you're monitoring PyPI somehow to 
> determine when new releases are made?

Yup; that is how I update an internal PyPI mirror we have (and this 'new' 1.0.1 
release is available as part of the daily sync). 

> Is it possible to also monitor when new files are 
> uploaded?

It may be possible. But I want to keep the implementation simple. I think 
release 
editing happens only rarely. To force a rebuild all I have to do is to "rm -rf" 
the 
build log; and the build automatically happens the subsequent day (that is what 
I 
did with argparse-1.0.1 today).

BUT, in future there are plans to implement some sort of smart notification to 
authors letting them know that a build of their package fails (only if they 
sign-up 
in first place). And things like that.

> At least in the case where only the build 
> (e.g. setup.py) is broken, it really doesn't 
> seem inappropriate to call it the same release.

Well, personally I would make a "post-release". Maybe 1.0.1.1 or, if one is 
using 
setuptools, 1.0.1-r453 as explained here - 
http://peak.telecommunity.com/DevCenter/
setuptools#specifying-your-project-s-version - in which case the actual version 
number would still remain 1.0.1.

I didn't see the explanation in your link (and I've never had any luck 
navigating the
setuptools documentation) but assuming this ever happens again (which I hope it
won't), a 1.0.1-rXXX sounds fine to me.

I'm assuming that for this one time you'll just "rm -rf" the build log. (Let me 
know
if that's not true.) Thanks for all the info on what you guys are working on - 
it's
good for me to be aware of what these technologies require of the release 
process. =)

Yup, I did 'rm -rf' yesterday. Take a look at:

  http://pypm.activestate.com/list-a.html#argparse

(aside - would you be interested in trying out PyPM private beta and giving 
your 
valuable feedback?)

Excellent - all white. =) Thanks!

And sure, I'm happy to try out PyPM. Thanks!