[Python-Dev] Outlook release on SourceForge
Tim Peters
tim.one at comcast.net
Tue Aug 12 23:08:54 EDT 2003
More information about the Python-Dev mailing list
Tue Aug 12 23:08:54 EDT 2003
- Previous message: [Python-Dev] Outlook release on SourceForge
- Next message: [Python-Dev] Make it an error to use __slots__ with classicclasses
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Tim] >> I find setting up an SF file release to be obscure but actually very >> quick and easy once you figure it out. [Michael Hudson] > Maybe I just never figured it out, then. Perhaps we should go back to > putting full releases up there -- but I found dealing with that thing > a serious hassle for 221c1 & 2. I'm not pushing for releasing Python on SF again -- while I think that would work OK now, it would be pointless thrashing (a change without good reason). OTOH, I think it helps spambayes to climb the SF rankings because that's a way to get some publicity for a project that isn't nearly as well known as Python. Yet <wink>.
- Previous message: [Python-Dev] Outlook release on SourceForge
- Next message: [Python-Dev] Make it an error to use __slots__ with classicclasses
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list