Moving distribute_setup.py
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
so we can use the PSF certificate and provide a better security scheme
I guess we can do the change in zc.buildout and distribute and once it's working, add a permanent redirect on the old address
That'll also take care of the bad uptimes I have on my cheap server
Any concerns ?
Cheers
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
so we can use the PSF certificate and provide a better security scheme
Yay!
I guess we can do the change in zc.buildout and distribute and once it's working, add a permanent redirect on the old address
You mean from the old to the new?
That'll also take care of the bad uptimes I have on my cheap server
Any concerns ?
Not from me.
Jim
Sounds good to me. See release.py in the root of distribute which uploads that file as part of the release process. It would be nice if that continues to work after the move. How is access controlled to that resource?
-----Original Message----- From: Distutils-SIG [mailto:distutils-sig- bounces+jaraco=jaraco.com@python.org] On Behalf Of Jim Fulton Sent: Thursday, 14 February, 2013 12:33 To: Tarek Ziadé Cc: distutils-sig@python.org Subject: Re: [Distutils] Moving distribute_setup.py
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup .py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
so we can use the PSF certificate and provide a better security scheme
Yay!
I guess we can do the change in zc.buildout and distribute and once it's working, add a permanent redirect on the old address
You mean from the old to the new?
That'll also take care of the bad uptimes I have on my cheap server
Any concerns ?
Not from me.
Jim
-- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
On 2/14/13 7:47 PM, Jason R. Coombs wrote:
Sounds good to me. See release.py in the root of distribute which uploads that file as part of the release process. It would be nice if that continues to work after the move. How is access controlled to that resource?
So what will need to be done is to tweak release.py so it does a POST if the file using the user in .pypirc
I can isolate that feature, as I said in the previous mail
On 2/14/13 6:32 PM, Jim Fulton wrote:
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
By POSTing a multipart/form-data, like what the upload command does for sdists : http://hg.python.org/cpython/file/0f827775f7b7/Lib/distutils/command/upload....
I can write a small script that does it (bascially rip off upload.upload_file() and remove the part about the metadata)
We could also write a custom sdist that does this, with an extra_dist_files, but oh well.. :)
so we can use the PSF certificate and provide a better security scheme
Yay!
I guess we can do the change in zc.buildout and distribute and once it's working, add a permanent redirect on the old address
You mean from the old to the new?
yeah
That'll also take care of the bad uptimes I have on my cheap server
Any concerns ?
Not from me.
Jim
On Thu, Feb 14, 2013 at 1:52 PM, Tarek Ziadé tarek@ziade.org wrote:
On 2/14/13 6:32 PM, Jim Fulton wrote:
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
By POSTing a multipart/form-data, like what the upload command does for sdists : http://hg.python.org/cpython/file/0f827775f7b7/Lib/distutils/command/upload....
Thanks. I'll look at that.
Jim
On Thu, Feb 14, 2013 at 1:52 PM, Tarek Ziadé tarek@ziade.org wrote:
On 2/14/13 6:32 PM, Jim Fulton wrote:
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
By POSTing a multipart/form-data, like what the upload command does for sdists : http://hg.python.org/cpython/file/0f827775f7b7/Lib/distutils/command/upload....
I can write a small script that does it (bascially rip off upload.upload_file() and remove the part about the metadata)
We could also write a custom sdist that does this, with an extra_dist_files, but oh well.. :)
Hm. I just tried to do this with ez_setup.py for setuptools, and PyPI's complaining that a .py file isn't a valid distribution. (I'm using the web interface, not the upload command, but same basic idea.)
AFAICT, we'll need the PyPI admins to implement support for .py uploads for this to work.
On 2/14/13 8:21 PM, PJ Eby wrote:
On Thu, Feb 14, 2013 at 1:52 PM, Tarek Ziadé tarek@ziade.org wrote:
On 2/14/13 6:32 PM, Jim Fulton wrote:
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to :https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
By POSTing a multipart/form-data, like what the upload command does for sdists : http://hg.python.org/cpython/file/0f827775f7b7/Lib/distutils/command/upload....
I can write a small script that does it (bascially rip off upload.upload_file() and remove the part about the metadata)
We could also write a custom sdist that does this, with an extra_dist_files, but oh well.. :)
Hm. I just tried to do this with ez_setup.py for setuptools, and PyPI's complaining that a .py file isn't a valid distribution. (I'm using the web interface, not the upload command, but same basic idea.)
AFAICT, we'll need the PyPI admins to implement support for .py uploads for this to work.
Oh you are right, I have not noticed that,
we need to add *.py here: https://bitbucket.org/loewis/pypi/src/f18ce0fbe947c1ce778761ea81d6704572cebb...
Will poke Catalog-sig
On Thu, Feb 14, 2013 at 2:24 PM, Tarek Ziadé tarek@ziade.org wrote:
On 2/14/13 8:21 PM, PJ Eby wrote:
On Thu, Feb 14, 2013 at 1:52 PM, Tarek Ziadé tarek@ziade.org wrote:
On 2/14/13 6:32 PM, Jim Fulton wrote:
On Thu, Feb 14, 2013 at 11:41 AM, Tarek Ziadé tarek@ziade.org wrote:
Hey
As Marc-André suggested, it would be a good thing to move the bootstrapping file to
:https://pypi.python.org/packages/source/d/distribute/distribute_setup.py
+1
I need to do something similar for buildout bootstrap files. How are you accomplishing this?
By POSTing a multipart/form-data, like what the upload command does for sdists :
http://hg.python.org/cpython/file/0f827775f7b7/Lib/distutils/command/upload....
I can write a small script that does it (bascially rip off upload.upload_file() and remove the part about the metadata)
We could also write a custom sdist that does this, with an extra_dist_files, but oh well.. :)
Hm. I just tried to do this with ez_setup.py for setuptools, and PyPI's complaining that a .py file isn't a valid distribution. (I'm using the web interface, not the upload command, but same basic idea.)
AFAICT, we'll need the PyPI admins to implement support for .py uploads for this to work.
Oh you are right, I have not noticed that,
we need to add *.py here: https://bitbucket.org/loewis/pypi/src/f18ce0fbe947c1ce778761ea81d6704572cebb...
Will poke Catalog-sig
Actually, there's another potential problem I just thought of. Normally, PyPI rejects repeated uploads of the same filename, so updating these could be a problem, unless there's an option to replace an existing file. (Because versioned bootstrap scripts would mean we can't give out a canonical URL to download the "current version" of a project.)
participants (4)
-
Jason R. Coombs -
Jim Fulton -
PJ Eby -
Tarek Ziadé