Looking at a bug report Fred forwarded, I realized that after py-howto.sourceforge.net was set up, www.python.org/doc/howto was never changed to redirect to the SF site instead. As of this afternoon, that's now done; links on www.python.org have been updated, and I've added the redirect.
Question: is it worth blowing away the doc/howto/ tree now, or should it just be left there, inaccessible, until work on www.python.org resumes?
--amk
Andrew Kuchling writes:
Looking at a bug report Fred forwarded, I realized that after py-howto.sourceforge.net was set up, www.python.org/doc/howto was never changed to redirect to the SF site instead. As of this afternoon, that's now done; links on www.python.org have been updated, and I've added the redirect.
Question: is it worth blowing away the doc/howto/ tree now, or should it just be left there, inaccessible, until work on www.python.org resumes?
Andrew, It looks like I never replied to this. It's probably dropped off your radar, but I'd say the answer is that the files on parrot should be discarded sooner rather than later -- when we actually manage to work on python.org we're that much more likely to have forgetten the redirection entirely!
-Fred
On Mon, May 28, 2001 at 02:20:01PM -0400, Fred L. Drake, Jr. wrote:
It looks like I never replied to this. It's probably dropped off your radar, but I'd say the answer is that the files on parrot should be discarded sooner rather than later -- when we actually manage to
Done. Out of paranoia about doing 'rm -rf' within www.python.org's tree, the files aren't deleted; instead I just moved them to my home directory on parrot.
--amk
participants (2)
-
Andrew Kuchling -
Fred L. Drake, Jr.