This Project Has Not Released Any Files
[Tim Peters]
From BeOpen.com's POV, so long as they were paying major bills, they would rather have download traffic tickle their ad banners than SF's ad banners.
Even though this should have been clear to me all the time, stating it explicitly triggers alarms for me. I just checked, and it appears that Python 2.0 is not available for download via ftp. In particular, it is not available via ftp from ftp.python.org! If it was there, mirrors all over the world would pick it up and bring it in a location near me (ftp.fu-berlin.de would be nearest) (*). So while making it available on SF may indeed give no advantage, making it available on python.org would provide users with alternative download locations, so that I don't feel the bandwidth limitation that Web download from pythonlabs.com produces. That would be a clear advantage to me, at least. Of course, having ftp mirrors would mean that many downloads do not tickle anybody's ad banners - which would probably be in the interest of other users as well, just not in the interest of BeOpen. So I'm curious how this conflict of interest is resolved... Regards, Martin (*) ftp://ftp.python.org/python/src/README does not even mention Python 2.0, and ftp://ftp.python.org/python/src/README.ftp says Note that some mirrors only collect the this directory (src), and the doc and contrib siblings, while the ftp master site, <URL:ftp://ftp.python.org/>, has much more. "Much more" may be true, just nothing recent... I probably should ask ftpmaster.python.org to put Python-2.0.tar.gz in that directory.
On Thu, Oct 19, 2000 at 07:31:58PM +0200, Martin v. Loewis wrote:
(*) ftp://ftp.python.org/python/src/README does not even mention Python 2.0, and ftp://ftp.python.org/python/src/README.ftp says
Unless one of the BeOpen Pythoneers is already going to do this, I'll go ahead and drop the relevant files into places. Guys? While we're at it, how about making the filenames for the source code consistent? -rw-r--r-- 1 guido psa 2533053 Apr 13 1999 py152.tgz -rw-r--r-- 1 1103 psa 2259957 Oct 31 1998 pyth151.tgz -rw-r--r-- 1 guido psa 1907724 May 31 1995 python1.2.tar.gz -rw-r--r-- 1 guido psa 2037062 Oct 12 1995 python1.3.tar.gz -rw-r--r-- 1 guido psa 2252481 Oct 25 1996 python1.4.tar.gz -rw-r--r-- 1 guido psa 2904353 Jan 3 1998 python1.5.tar.gz I like pythonX.X.tar.gz best, and will change the filenames (leaving bc-compat symlinks for py152.tgz and pyth151.tgz) unless vetoed. Though isn't the standard GNU naming convention more like python-1.5.tar.gz? --amk
Andrew Kuchling <akuchlin@mems-exchange.org>:
I like pythonX.X.tar.gz best, and will change the filenames (leaving bc-compat symlinks for py152.tgz and pyth151.tgz) unless vetoed. Though isn't the standard GNU naming convention more like python-1.5.tar.gz?
It is, and I wish we'd move to it as did the Perl guys. It makes life substantially easier to have really uniform naming conventions, especially for programs like the Metalabs file clerk. -- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a> Don't ever think you know what's right for the other person. He might start thinking he knows what's right for you. -- Paul Williams, `Das Energi'
On Thu, Oct 19, 2000 at 01:42:19PM -0400, Andrew Kuchling wrote:
On Thu, Oct 19, 2000 at 07:31:58PM +0200, Martin v. Loewis wrote:
(*) ftp://ftp.python.org/python/src/README does not even mention Python 2.0, and ftp://ftp.python.org/python/src/README.ftp says
Unless one of the BeOpen Pythoneers is already going to do this, I'll go ahead and drop the relevant files into places. Guys?
Please... just do it.
... I like pythonX.X.tar.gz best, and will change the filenames (leaving bc-compat symlinks for py152.tgz and pyth151.tgz) unless vetoed. Though isn't the standard GNU naming convention more like python-1.5.tar.gz?
I'm with Eric -- go for the GNU standard. Cheers, -g -- Greg Stein, http://www.lyra.org/
On Thu, Oct 19, 2000 at 11:54:36AM -0700, Greg Stein wrote:
On Thu, Oct 19, 2000 at 01:42:19PM -0400, Andrew Kuchling wrote:
Unless one of the BeOpen Pythoneers is already going to do this, I'll go ahead and drop the relevant files into places. Guys?
Please... just do it.
I charged ahead and did it anyway; the Pythoneers can spank me for it later. (Worse, maybe they'll do something *bad* to me...) There were already doc/1.6/ and doc/2.0/ directories, and binaries (Windows, RPMs) were in /pub/python/2.0/, along with the source. So I only touched /pub/python/src/. All the releases and betas are now consistently named python-X.Y.Z.tar.gz. I've left symlinks in place for the original filenames of the 1.5.1, 1.5.2 and 1.6 final releases, but didn't bother making links for releases older than 1.5.1 or for beta versions, so any FTP URLs pointing directly to those files will be broken. --amk
"GS" == Greg Stein <gstein@lyra.org> writes:
GS> On Thu, Oct 19, 2000 at 01:42:19PM -0400, Andrew Kuchling wrote:
On Thu, Oct 19, 2000 at 07:31:58PM +0200, Martin v. Loewis wrote:
(*) ftp://ftp.python.org/python/src/README does not even mention Python 2.0, and ftp://ftp.python.org/python/src/README.ftp says
Unless one of the BeOpen Pythoneers is already going to do this, I'll go ahead and drop the relevant files into places. Guys?
GS> Please... just do it. In the interest of making the distribution as widely available as possible, I've placed files on SourceForge and at http://www.python.org/2.0/
... I like pythonX.X.tar.gz best, and will change the filenames (leaving bc-compat symlinks for py152.tgz and pyth151.tgz) unless vetoed. Though isn't the standard GNU naming convention more like python-1.5.tar.gz?
GS> I'm with Eric -- go for the GNU standard. I used the file name conventions that we used throughout the 2.0 release cycle, e.g. Python-2.0.tar.gz. I don't know if that's the GNU standard or not (didn't realize it was a standard; don't know where to find said standard; or is it just a custom?) Jeremy
On Fri, Oct 20, 2000 at 12:28:19PM -0400, Jeremy Hylton wrote:
release cycle, e.g. Python-2.0.tar.gz. I don't know if that's the GNU standard or not (didn't realize it was a standard; don't know where to find said standard; or is it just a custom?)
See http://www.cs.utah.edu/dept/old/texinfo/standards/standards.html#SEC24 Though I think here the standard is just codifying an existing custom that's proved convenient. www.fsf.org seems unresponsive at the moment, hence the strange link; is *every* Web site in the world breaking today for some reason? --amk
Jeremy Hylton writes:
In the interest of making the distribution as widely available as possible, I've placed files on SourceForge and at http://www.python.org/2.0/
There's a separate python-rpms "Package"; the RPM files should go there (I think). -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs Team Member
On Thu, Oct 19, 2000 at 07:31:58PM +0200, Martin v. Loewis wrote:
... Of course, having ftp mirrors would mean that many downloads do not tickle anybody's ad banners - which would probably be in the interest of other users as well, just not in the interest of BeOpen. So I'm curious how this conflict of interest is resolved...
Stating that a "conflict of interest" even EXISTS is a rather sorry statement on things. -g -- Greg Stein, http://www.lyra.org/
[Tim, on 19 October]
From BeOpen.com's POV, so long as they were paying major bills, they would rather have download traffic tickle their ad banners than SF's ad banners.
[Martin v. Loewis]
Even though this should have been clear to me all the time, stating it explicitly triggers alarms for me. ... Of course, having ftp mirrors would mean that many downloads do not tickle anybody's ad banners - which would probably be in the interest of other users as well, just not in the interest of BeOpen. So I'm curious how this conflict of interest is resolved...
I hope it's clear now how it got resolved: at the time I wrote that, the PythonLabs guys were officially but secretly unemployed. The issue of distributing Python was one bone of contention at The End, but not the mongoose that pecked the python's eyes out. or-if-you're-not-american-it-wasn't-the-straw-that-tickled-the- camel-to-death-ly y'rs - tim
participants (7)
-
Andrew Kuchling -
Eric S. Raymond -
Fred L. Drake, Jr. -
Greg Stein -
Jeremy Hylton -
Martin v. Loewis -
Tim Peters