I'm getting ready for the release of alpha 2. Tomorrow afternoon (around 5:30pm east coast time) I'm going on vacation for the rest of the week, followed by a business trip most of the week after. Obviously, I'm anxious to release a solid alpha tomorrow. Please, send only simple or essential patches between now and the release date! --Guido van Rossum (home page: http://www.python.org/~guido/)
On Mon, 10 Apr 2000, Guido van Rossum wrote:
I'm getting ready for the release of alpha 2. Tomorrow afternoon (around 5:30pm east coast time) I'm going on vacation for the rest of the week, followed by a business trip most of the week after.
Obviously, I'm anxious to release a solid alpha tomorrow.
Please, send only simple or essential patches between now and the release date!
Jeremy reminded me that my new httplib.py is still pending integration. There are two possibilities: 1) My httplib.py uses a new name, or goes into a "net" package. We check it in today, and I follow up with patches to fold in post-1.5.2 compatibility items (such as the SSL stuff). 2) httplib.py will remain in the same place, so the compat changes must happen first. In both cases, I will also need to follow up with test and doc. IMO, we go with "net.httplib" and check it in today. Cheers, -g -- Greg Stein, http://www.lyra.org/
Please, send only simple or essential patches between now and the release date!
Jeremy reminded me that my new httplib.py is still pending integration.
There will be another alpha release after I'm back -- I think this isn't that urgent. (Plus, just because you're you, you'd have to mail me a wet signature. :-) I am opposed to a net.* package until the reorganization discussion has resulted in a solid design. --Guido van Rossum (home page: http://www.python.org/~guido/)
On Mon, 10 Apr 2000, Guido van Rossum wrote:
Please, send only simple or essential patches between now and the release date!
Jeremy reminded me that my new httplib.py is still pending integration.
There will be another alpha release after I'm back -- I think this isn't that urgent.
True, but depending on location, it also has zero impact on the release. In other words: added functionality for testing, with no potential for breakage.
(Plus, just because you're you, you'd have to mail me a wet signature. :-)
You've got one on file already :-) [ I sent it back in December; was it misplaced, and I need to resend? ]
I am opposed to a net.* package until the reorganization discussion has resulted in a solid design.
Not a problem. Mine easily replaces httplib.py in its current location. It is entirely backwards compat. A new class is used to get the new functionality, and a compat "HTTP" class is provided (leveraging the new HTTPConnection class). Cheers, -g -- Greg Stein, http://www.lyra.org/
Jeremy reminded me that my new httplib.py is still pending integration.
There will be another alpha release after I'm back -- I think this isn't that urgent.
True, but depending on location, it also has zero impact on the release. In other words: added functionality for testing, with no potential for breakage.
You're just asking for exposure. But unless it's installed as httplib.py, it won't get much more exposure than if you put it on your website and post an announcement to c.l.py, I bet.
(Plus, just because you're you, you'd have to mail me a wet signature. :-)
You've got one on file already :-)
[ I sent it back in December; was it misplaced, and I need to resend? ]
I was just teasing. Our lawyer believes that you cannot send in a signature for code that you will contribute in the future; but I really don't care enough to force you to send another one...
I am opposed to a net.* package until the reorganization discussion has resulted in a solid design.
Not a problem. Mine easily replaces httplib.py in its current location. It is entirely backwards compat. A new class is used to get the new functionality, and a compat "HTTP" class is provided (leveraging the new HTTPConnection class).
I thought you said there was some additional work on compat changes? I quote: | 2) httplib.py will remain in the same place, so the compat changes must | happen first. Oh well, send it to Jeremy and he'll check it in if it's ready. But not without a test suite and documentation. --Guido van Rossum (home page: http://www.python.org/~guido/)
On Mon, 10 Apr 2000, Guido van Rossum wrote:
... You're just asking for exposure. But unless it's installed as httplib.py, it won't get much more exposure than if you put it on your website and post an announcement to c.l.py, I bet.
Hmm. Good point :-)
...
(Plus, just because you're you, you'd have to mail me a wet signature. :-)
You've got one on file already :-)
[ I sent it back in December; was it misplaced, and I need to resend? ]
I was just teasing.
:-)
...
I am opposed to a net.* package until the reorganization discussion has resulted in a solid design.
Not a problem. Mine easily replaces httplib.py in its current location. It is entirely backwards compat. A new class is used to get the new functionality, and a compat "HTTP" class is provided (leveraging the new HTTPConnection class).
I thought you said there was some additional work on compat changes?
Oops. Yah. It would become option (2) (add compat stuff first) by dropping it over the current one. Mostly, I'm concerned about the SSL stuff that was added, but there may be other things (need to check the CVS logs). For example, there was all that stuff dealing with the errors (which never went in, I believe?).
... Oh well, send it to Jeremy and he'll check it in if it's ready. But not without a test suite and documentation.
Ah. Well, then it definitely won't go in now :-). It'll take a bit to set up the tests and docco. Well... thanx for the replies. When I get the stuff ready, I'll speak up again. And yes, I do intend to ensure this stuff is ready in time for 1.6. Cheers, -g p.s. and I retract my request for inclusion of davlib. I think there is still some design work to do on that guy. -- Greg Stein, http://www.lyra.org/
p.s. and I retract my request for inclusion of davlib. I think there is still some design work to do on that guy.
But it should at least be available outside the distro! The Vaults of Parnassus don't list it -- so it don't exist! :-) --Guido van Rossum (home page: http://www.python.org/~guido/)
On Mon, 10 Apr 2000, Guido van Rossum wrote:
p.s. and I retract my request for inclusion of davlib. I think there is still some design work to do on that guy.
But it should at least be available outside the distro! The Vaults of Parnassus don't list it -- so it don't exist! :-)
D'oh! I forgot to bring it over from my alternate plane of reality. ... Okay. I've synchronized the universes. Parnassus now contains a number of records for my Python stuff (well, submitted at least). Thanx for the nag :-) Cheers, -g -- Greg Stein, http://www.lyra.org/
participants (2)
-
Greg Stein -
Guido van Rossum