
Hi,
I would like to upload an egg to the cheeseshop, but I have a problem because my network is behind a proxy. My configuration is unusual in the sense that my network has no DNS server, and everything is done through the proxy: proxy has to be used to access an url:
Submitting dist/numscons-0.3.1-py2.5.egg to http://www.python.org/pypi (-2, 'Name or service not known')
I know for sure I can access pypi, and that this is a proxy related problem (other python projects relying on urllib2 had similar problems, e.g. bzr).
cheers,
David

--On 25. Januar 2008 15:06:17 +0900 David Cournapeau david@ar.media.kyoto-u.ac.jp wrote:
Hi,
I would like to upload an egg to the cheeseshop, but I have a
problem because my network is behind a proxy. My configuration is unusual in the sense that my network has no DNS server, and everything is done through the proxy: proxy has to be used to access an url:
Submitting dist/numscons-0.3.1-py2.5.egg to http://www.python.org/pypi (-2, 'Name or service not known')
I know for sure I can access pypi, and that this is a proxy related problem (other python projects relying on urllib2 had similar problems, e.g. bzr).
Not an answer but you can upload your files to PyPI manually using the web interface.
Andreas

Andreas Jung wrote:
--On 25. Januar 2008 15:06:17 +0900 David Cournapeau david@ar.media.kyoto-u.ac.jp wrote:
Hi,
I would like to upload an egg to the cheeseshop, but I have a
problem because my network is behind a proxy. My configuration is unusual in the sense that my network has no DNS server, and everything is done through the proxy: proxy has to be used to access an url:
Submitting dist/numscons-0.3.1-py2.5.egg to http://www.python.org/pypi (-2, 'Name or service not known')
I know for sure I can access pypi, and that this is a proxy related problem (other python projects relying on urllib2 had similar problems, e.g. bzr).
Not an answer but you can upload your files to PyPI manually using the web interface.
Andreas
Yes, sure :) This and ssh tunneling work, but that's not ideal.
thanks,
David

On Sat, Jan 26, 2008 at 08:52:09PM +0900, David Cournapeau wrote:
Yes, sure :) This and ssh tunneling work, but that's not ideal.
Have you tried the ``http_proxy`` environment variable?
(Didn't test, so I dunno. Just poked around the urllib source a bit and found a blurb about <scheme>_proxy environment variables)

James William Pye wrote:
On Sat, Jan 26, 2008 at 08:52:09PM +0900, David Cournapeau wrote:
Yes, sure :) This and ssh tunneling work, but that's not ideal.
Have you tried the ``http_proxy`` environment variable?
(Didn't test, so I dunno. Just poked around the urllib source a bit and found a blurb about <scheme>_proxy environment variables)
That's not the problem (and I have the variable defined to a correct value). The problem is that most of the time, the proxy is used to get a connection, but not to translate the url into an IP. In my case, this is needed. For example, ping google.com does not work on my machine: not because of ICMP blocking, but because google.com is not resolved to an IP. Only the proxy can do that
cheers,
David

On Sun, Jan 27, 2008 at 02:06:40PM +0900, David Cournapeau wrote:
...
yeah, that's right.
Looking at the upload command in 2.5's branch, httplib is used directly, so the http_proxy environment variable isn't even being referenced on ``./setup.py upload``. Thus the name resolution error.
participants (3)
-
Andreas Jung
-
David Cournapeau
-
James William Pye