[lxml-dev] Please upload your sdists on PyPI
Hi there, could you please make _all_ releases of lxml available on PyPI. All buildout that haven't used a pinned version broke over the last days due the unavailability of codespeak since 2.3.0a2 has no releases. Thanks, Andreas
On 8/24/2010 8:37 AM, Andreas Jung wrote:
Hi there,
could you please make _all_ releases of lxml available on PyPI.
All buildout that haven't used a pinned version broke over the last days due the unavailability of codespeak since 2.3.0a2 has no releases.
Hmm, shouldn't buildout use 2.2.7, that is in fact hosted in PyPI? 2.3alpha2 *was* once released to PyPI, but it was deleted later on: http://article.gmane.org/gmane.comp.python.lxml.devel/5496/match=2.3alpha At least for me "pip install lxml" downloads 2.2.7, not 2.3*. -srid
2010/8/25 Sridhar Ratnakumar <sridharr@activestate.com>
On 8/24/2010 8:37 AM, Andreas Jung wrote:
Hi there,
could you please make _all_ releases of lxml available on PyPI.
All buildout that haven't used a pinned version broke over the last days due the unavailability of codespeak since 2.3.0a2 has no releases.
Hmm, shouldn't buildout use 2.2.7, that is in fact hosted in PyPI?
2.3alpha2 *was* once released to PyPI, but it was deleted later on: http://article.gmane.org/gmane.comp.python.lxml.devel/5496/match=2.3alpha
Released is released!
At least for me "pip install lxml" downloads 2.2.7, not 2.3*.
We don't care about pip - incomplete or badly maintained releases broke the buildouts of many people...please ensure that the lxml are clean. Thanks, Andreas
-srid
Andreas Jung, 25.08.2010 06:53:
2010/8/25 Sridhar Ratnakumar
On 8/24/2010 8:37 AM, Andreas Jung wrote:
could you please make _all_ releases of lxml available on PyPI.
All buildout that haven't used a pinned version broke over the last days due the unavailability of codespeak since 2.3.0a2 has no releases.
At least setuptools handles this as expected, as does pip, as reported. Sounds like buildout could also be fixed.
Hmm, shouldn't buildout use 2.2.7, that is in fact hosted in PyPI?
2.3alpha2 *was* once released to PyPI, but it was deleted later on: http://article.gmane.org/gmane.comp.python.lxml.devel/5496/match=2.3alpha
Released is released!
Well, yes, but I didn't put the sdists up on PyPI exactly because I didn't want users to install it by default. Otherwise, setuptools would grab the latest distribution regardless of the advertised state of stability. In the current state of affairs, users will continue to get the latest stable release when they do not specify a version. I think that's what most people want. Developer releases are not meant for production. Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefan Behnel wrote:
Andreas Jung, 25.08.2010 06:53:
2010/8/25 Sridhar Ratnakumar
On 8/24/2010 8:37 AM, Andreas Jung wrote:
could you please make _all_ releases of lxml available on PyPI.
All buildout that haven't used a pinned version broke over the last days due the unavailability of codespeak since 2.3.0a2 has no releases.
At least setuptools handles this as expected, as does pip, as reported.
Sounds like buildout could also be fixed.
Hmm, shouldn't buildout use 2.2.7, that is in fact hosted in PyPI?
2.3alpha2 *was* once released to PyPI, but it was deleted later on: http://article.gmane.org/gmane.comp.python.lxml.devel/5496/match=2.3alpha
Released is released!
Well, yes, but I didn't put the sdists up on PyPI exactly because I didn't want users to install it by default. Otherwise, setuptools would grab the latest distribution regardless of the advertised state of stability.
In the current state of affairs, users will continue to get the latest stable release when they do not specify a version. I think that's what most people want. Developer releases are not meant for production.
Once again: the 2.3.0a2 release had no release files and the default behavior of setuptools or whatever is involved is to follow the homepage URL at http://codespeak.net/lxml. I don't think that buildout is doing something special here since it used setuptools transparently afaik. Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMdLN5AAoJEADcfz7u4AZjz/cLwMjPNStiSLLFSkYwQAfSgSss FHpMpZeRMQAYrCbuDwp0GLIycNNTPW0m1IMpHU26OJ9EY5yA3cn+TqbLUALY2XxD 4xggoslKuMAN6EhGcH6twdoe/nWNu2o7kX8jWtbrz4LMOYjIThRk34JOZ9cMK9u4 u3ndXI9LVzDSgSCDazEO1HDvaURbuFrd/nDawwYbC3vYKGiktwv+ujTn+pU1jQ5J uaVe8xyT9DCbA0dwC8pVhzZ/0j99m062Cqvw+sVxzp5HSqzZoXb8vEv8pRWVGpaU zrSkTaRrcy4drR+QBW60eV1cWjFaJPGrr44/qx8fgdB0zYx8tBFj6dnWiRyLOZ2N 3qgErbDc5Q7jkDUlnyf9Q9mnG91vvzcWLgAmg7I6lG2OoTTzReaudQHSzdbXKaD0 mQPWa+bT7TO4rMUW2acc2jS0UE4eix66da1KHe36RtBYV24bWn0VCi3lt0pwXldq 5rPvb3tW3EtpVdn3KSFmQZ185qqu/6w= =h7eI -----END PGP SIGNATURE-----
Andreas Jung, 25.08.2010 08:08:
Stefan Behnel wrote:
At least setuptools handles this as expected, as does pip, as reported.
In the current state of affairs, users will continue to get the latest stable release when they do not specify a version. I think that's what most people want. Developer releases are not meant for production.
Once again: the 2.3.0a2 release had no release files and the default behavior of setuptools or whatever is involved is to follow the homepage URL at http://codespeak.net/lxml. I don't think that buildout is doing something special here since it used setuptools transparently afaik.
Well, I didn't try it, but quite obviously, it does. Plain setuptools works for me and others. Note that the 2.3 pages do now have a download URL, that's what seems to do the trick for setuptools. Personally, I think the right fix would be a client-side download option that depends on the "Development Status" category. Setuptools, buildout & friends should prefer the most stable version by default, instead of just taking any "latest" version they find. Stefan
Stefan Behnel wrote:
Personally, I think the right fix would be a client-side download option that depends on the "Development Status" category. Setuptools, buildout & friends should prefer the most stable version by default, instead of just taking any "latest" version they find.
This is true for new releases of buildout. It's also configurable in your buildout.cfg. Andreas is just likely stuck in the stone age ;-) Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
participants (4)
-
Andreas Jung -
Chris Withers -
Sridhar Ratnakumar -
Stefan Behnel