Hosting .egg on pypi.python.org

[GoogleCodeExporter]

Looks like currently psutil  .tar.gz downloads are hosted on Google Code only 
(*.googlecode.com).

I suggest you automatize the release process and also put a copy of the egg on 
pypi.python.org too to increase the accessibility of this very nice package. 
Reasons: reliability, accessing it countries like China, etc.

Here is a tutorial:

http://opensourcehacker.com/2012/08/14/high-quality-automated-package-releases-f
or-python-with-zest-releaser/

Original issue reported on code.google.com by mi...@redinnovation.com on 4 Dec 2012 at 11:27

[GoogleCodeExporter]

Google Code is not accessible from China? Really?

Original comment by g.rodola on 5 Dec 2012 at 12:04

[GoogleCodeExporter]

It's not constantly blocked, but it has happened for my projects in the past.

All Google services use the same front end web server which China tends to 
block by IP.

Original comment by mi...@redinnovation.com on 5 Dec 2012 at 12:06

[GoogleCodeExporter]

Well I'm sorry, but I'm not willing to scatter resources across multiple 
domains because of the stupid China government, also because producing and 
uploading the various exes, tarballs etc. is already a considerable time 
consuming task.
Also, I think that if the *whole* Google infrastructure gets blocked, not being 
able to download psutil should be the least of your problems.

Original comment by g.rodola on 5 Dec 2012 at 12:30

• Changed state: WontFix

[GoogleCodeExporter]

I realize that my last message might sound a bit rude or even a bit personal.
I'm sorry: that wasn't my intention.

Original comment by g.rodola on 5 Dec 2012 at 12:34

[GoogleCodeExporter]

I mean if you can automatize the whole process, so there wouldn't be extra 
effort?

What parts in the release process are such that you cannot automatize?

Original comment by mi...@redinnovation.com on 5 Dec 2012 at 12:37

[GoogleCodeExporter]

Thus, trying to point you to the Python egg release tools.

I don't want to say you should do it, but maybe you should take a look on them, 
as the process of producing and uploading exes is something no one wants to do 
:) 

Original comment by mi...@redinnovation.com on 5 Dec 2012 at 12:39

[GoogleCodeExporter]

Thanks, I already use a script which generates the various Windows installers 
and uploads them on Google Code 
(http://code.google.com/p/support/wiki/ScriptedUploads).
I don't have one for uploading on pypi of course, but the effort needed to 
write one is not the point here.
It's the idea of scattering resources which I don't like.

Original comment by g.rodola on 5 Dec 2012 at 12:57

[GoogleCodeExporter]

I'll take a look at the linked article in the next day or so and see what the 
benefits are over our current approach. If there's not an appreciable amount of 
extra work then it may be worth adding for end user convenience reasons. 

Original comment by jlo...@gmail.com on 5 Dec 2012 at 12:58

[GoogleCodeExporter]

Ok great :) Windows installers are PITA, so I am not sure if this tip will give 
you any help / extra. Do what is the best for you.

Basically uploading to pypi should be just one command even when done by hand:

python setup.py sdist bdist_wininst upload

(incl. Windows installer)

http://docs.python.org/2/distutils/uploading.html

Original comment by mi...@redinnovation.com on 5 Dec 2012 at 1:04

[GoogleCodeExporter]

Issue 364 has been merged into this issue.

Original comment by g.rodola on 9 Apr 2013 at 5:07

[GoogleCodeExporter]

Reference for later review: 
http://docs.python.org/2/distutils/packageindex.html#package-index

Original comment by jlo...@gmail.com on 9 Apr 2013 at 5:09

[GoogleCodeExporter]

Actually you just need to run ``python setup.py upload`` after your release 
process.

Original comment by hubscher.remy on 9 Apr 2013 at 5:10