[Python-Dev] [Patch #101055] Cookie.py (original) (raw)
Thomas Wouters thomas@xs4all.net
Fri, 18 Aug 2000 23:04:01 +0200
- Previous message: [Python-Dev] Re: [Patches] [Patch #101055] Cookie.py
- Next message: [Python-Dev] [Patch #101055] Cookie.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Aug 18, 2000 at 04:48:37PM -0400, Andrew Kuchling wrote:
[ About adding Cookie.py including CVS history ]
I hate throwing away information that stands even a tiny chance of being useful; good thing the price of disk storage keeps dropping, eh? The version history might contain details that will be useful in future debugging or code comprehension, so I dislike losing it forever.
It would be moderately nice to have the versioning info, though I think Fred has a point when he says that it might be confusing for people: it would look like the file had been in the CVS repository the whole time, and it would be very hard to see where the file had been added to Python. And what about new versions ? Would this file be adopted by Python, would changes by the original author be incorporated ? How about version history for those changes ? The way it usually goes (as far as my experience goes) is that such files are updated only periodically. Would those updates incorporate the history of those changes as well ?
Unless Cookie.py is really split off, and we're going to maintain a separate version, I don't think it's worth worrying about the version history as such. Pointing to the 'main' version and it's history should be enough.
-- Thomas Wouters <thomas@xs4all.net>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
- Previous message: [Python-Dev] Re: [Patches] [Patch #101055] Cookie.py
- Next message: [Python-Dev] [Patch #101055] Cookie.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]