I started a library that tools can use to select a PyPI mirror, see
https://svn.python.org/packages/trunk/pypi/tools/mirrorlib.py
It currently only deals with mirror selection, but will be extended
to deal with mirror validation and key rollover as well.
For mirror selection, the objective is
The obvious question from a distutils person: Any plans to package the
lib and publish it on PyPI? (Maybe with a more specific name.)
Sure, will do (but I'd like to implement the missing features first).
It seems very few edits would be needed to make the lib compatible with
3.x. What is
IMHO, most of this has been resolved by means of the XML-RPC
interface via the .release_data() method:
http://wiki.python.org/moin/PyPiXmlRpc
If there's something missing, we should add it there.
Very clearly, most of egg-info is missing there. However, I
sense that people are very
Martin v. Löwis wrote:
IMHO, most of this has been resolved by means of the XML-RPC
interface via the .release_data() method:
http://wiki.python.org/moin/PyPiXmlRpc
If there's something missing, we should add it there.
Very clearly, most of egg-info is missing there. However, I
sense
On Mon, Sep 20, 2010 at 9:57 PM, M.-A. Lemburg m...@egenix.com wrote:
That's how I would have implemented it. Alas, this very
idea was just shot down.
I think most of the response was targeted at the EGG-INFO
meta-data format, not the information itself.
No, it's also the information itself.
On Mon, Sep 20, 2010 at 9:26 PM, Martin v. Löwis mar...@v.loewis.de wrote:
IMHO, most of this has been resolved by means of the XML-RPC
interface via the .release_data() method:
http://wiki.python.org/moin/PyPiXmlRpc
If there's something missing, we should add it there.
Very clearly, most
I think most of the response was targeted at the EGG-INFO
meta-data format, not the information itself.
My impression was otherwise: several posters clearly indicated
that they don't want exposition of this information (in whatever
form), as they expected it would hinder adoption of PEP 345.
Tarek Ziadé wrote:
On Mon, Sep 20, 2010 at 9:26 PM, Martin v. Löwis mar...@v.loewis.de wrote:
IMHO, most of this has been resolved by means of the XML-RPC
interface via the .release_data() method:
http://wiki.python.org/moin/PyPiXmlRpc
If there's something missing, we should add it there.
2010/9/20 M.-A. Lemburg m...@egenix.com:
Tarek Ziadé wrote:
On Mon, Sep 20, 2010 at 9:26 PM, Martin v. Löwis mar...@v.loewis.de
wrote:
IMHO, most of this has been resolved by means of the XML-RPC
interface via the .release_data() method:
http://wiki.python.org/moin/PyPiXmlRpc
If there's
Connection failed Service pypi.python.org
Date:Mon, 20 Sep 2010 15:58:57 -0500
Action: alert
Host:jacobian.org
Description: failed protocol test [HTTP] at INET[pypi.python.org:80]
via TCP
Your faithful employee,
monit
At 09:26 PM 9/20/2010 +0200, Martin v. Löwis wrote:
That's how I would have implemented it. Alas, this very
idea was just shot down.
Hm. When the issue was adding comments to PyPI, you mostly ignored
the strong opposition from people who didn't want to use the feature,
in order to support
Am 20.09.2010 23:20, schrieb P.J. Eby:
At 09:26 PM 9/20/2010 +0200, Martin v. Löwis wrote:
That's how I would have implemented it. Alas, this very
idea was just shot down.
Hm. When the issue was adding comments to PyPI, you mostly ignored the
strong opposition from people who didn't want
Any plans to package the lib and publish it on PyPI? (Maybe with a
more specific name.)
Sure, will do (but I'd like to implement the missing features first).
Nice.
It seems very few edits would be needed to make the lib compatible with
3.x.
I suppose you want to add missing features before
13 matches
Mail list logo
