[Grok-dev] easy_install -U grokproject gets me 0.7dev
ethan.jucovy at gmail.com
Sun Mar 16 17:04:39 EDT 2008
On Sun, Mar 16, 2008 at 3:29 PM, Martijn Faassen <faassen at startifact.com>
> Hi there,
> Today I tried to make sure I had the latest grokproject. Unfortunately
> easy_install -U grokproject gets me 0.7dev, which was never released,
> possibly because it pulls it directly from SVN trunk?
> Does this mean that when people install grokproject they get grokproject
> 0.7 immediately, including the z3c.autoinclude integration? That's not
> exactly the way we want to do releases, and I'm not even sure that'll
> work with Grok 0.11.x!
> What can be done about this? Remove the grokproject SVN URL?
I just tried `easy_install grokproject` in a clean environment and it ended
up pulling v0.6. `easy_install -U grokproject` seems to do the same for me
(v0.6) in both a clean environment and one with grokproject v0.6 already
installed. So I don't think you need to be worred; it's probably just
something about your particular environment. (For example, maybe you had a
copy of the trunk checkout already lying around and easy_install found it
That said, I just did a very cursory scan of how packages on PyPI use
`download_url`. (I couldn't find any documentation about its intended
meaning.) Most packages that I've seen don't actually specify a
download_url at all (which is too bad) but the ones that do seem to set it
to the particular tag that's being released. That would be more accurate
and also slightly safer; I've never really understood how easy_install works
but it does follow links so it's possible that your 0.7dev installation
somehow came about by easy_install noticing that download_url. You could
just automate that in setup.py before the next release --
version = 0.7
download_url="svn://svn.zope.org/repos/main/grokproject/tags/" + version,
and put a link to trunk somewhere in the long_description.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Grok-dev