Eric Lemoine wrote: > On Thu, Jul 10, 2008 at 3:24 PM, Matthew Russell > <[EMAIL PROTECTED]> wrote: >> Hi Eric, >> >> I'm sorry, but I'm not sure why PyPI isn't keeping the previous versions >> (Sean, you got an idea?) >> I started making svn tags of released versions, at version 1.0a4. >> Sean, can you make a tag of the 1.0b1 release (or I can if nothing has >> changed since you published to PyPI) >> >> Is there a particular feature that you rely on in 1.0a3? I'd be very >> surprised if you weren't able to upgrade to 1.0b1 (I don't believe there >> have been any external changes since then). > > MapFish 0.2 was released with GeoJSON=1.0a3 in setup.py. It makes > sense for use to do MapFish releases against given versions of > GeoJSON, Shapely and stuff, should one these components break backward > compatibility. > >> If this is not the case, then I'd be happy to help (If I can). >> Of course, you *should* be able to get hold of a copy of 1.0a3, but since we >> didn't make a tag at the time, this seems impossible, unless Sean has got a >> copy around somewhere. I take responsibility for this, since I maintain the >> package. >> I will ensure, all PyPI releases from 1.0a4 onwards have svn tags, thus if >> PyPI has a problem, or something like this happens again we can rebuild a >> distribution. > > Thanks, > > -- > Eric
It's entirely my fault; I'll put the old packages back up. Eric, did you see this post yesterday? http://compoundthinking.com/blog/index.php/2008/07/08/setuptools-package-indexes-and-releases/ It describes a recipe for turning a directory of eggs into a Python package index. It might be useful to do something like this for MapFish, and allow users to get a known good set with one command, like: $ easy_install -i http://.../mapfish/1 MapFish (the mapfish/1 directory could contain GeoJSON==1.0a3 or any other version you wanted.) Sean _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
