On Wed, Oct 8, 2008 at 12:51 AM, Dmitry Vasiliev <[EMAIL PROTECTED]> wrote:
>
> BTW, I think the following issues should be also marked as release blockers:
Agreed and done.
>
> - http://bugs.python.org/issue3714 (nntplib module broken by str to
> unicode conversion)
> - http://bugs.python.org/is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 7, 2008, at 4:28 PM, Guido van Rossum wrote:
15-Oct-2008 3.0 rc 2
05-Nov-2008 3.0 rc 3
19-Nov-2008 3.0 rc 4
03-Dec-2008 3.0 final
I've updated PEP 361 and the Google calendar with this schedule,
except that the PEP says that rc3 and r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 7, 2008, at 4:28 PM, Guido van Rossum wrote:
On Mon, Oct 6, 2008 at 5:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
So, we need to come up with a new release schedule for Python 3.0.
My
suggestion:
15-Oct-2008 3.0 beta 4
05-Nov-2008 3.0
Guido van Rossum wrote:
On Mon, Oct 6, 2008 at 5:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
So, we need to come up with a new release schedule for Python 3.0. My
suggestion:
15-Oct-2008 3.0 beta 4
05-Nov-2008 3.0 rc 2
19-Nov-2008 3.0 rc 3
03-Dec-2008 3.0 final
Given what still needs to be
On Mon, Oct 6, 2008 at 5:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> So, we need to come up with a new release schedule for Python 3.0. My
> suggestion:
>
> 15-Oct-2008 3.0 beta 4
> 05-Nov-2008 3.0 rc 2
> 19-Nov-2008 3.0 rc 3
> 03-Dec-2008 3.0 final
>
> Given what still needs to be done, is t
Antoine Pitrou <[EMAIL PROTECTED]> wrote:
> > - And then, getopt and optparse modules should work on bytestring
> > vectors, so that you can use sys.argvb without writing your own
> > argument parser. They don't currently.
>
> Then we will gradually start moving all modules even remotely re
Antoine Pitrou wrote:
Hi,
James Y Knight fuhm.net> writes:
- Having os.getcwdb isn't much use when you can't even run python in
the first place when the current directory has "bad" bytes in it.
I don't agree it's a similar problem. Python should be installed in a well-known
place with a s
Hi,
James Y Knight fuhm.net> writes:
>
> - Having os.getcwdb isn't much use when you can't even run python in
> the first place when the current directory has "bad" bytes in it.
I don't agree it's a similar problem. Python should be installed in a well-known
place with a sensible path. Of
Hi,
First of all, please read my document:
http://wiki.python.org/moin/Python3UnicodeDecodeError
I moved the document to a public wiki to allow anyone to edit it!
Le Tuesday 07 October 2008 05:22:09 James Y Knight, vous avez écrit :
> On Oct 6, 2008, at 8:52 PM, Benjamin Peterson wrote:
> > I'm
On Oct 6, 2008, at 8:52 PM, Benjamin Peterson wrote:
I'm not sure we do. Correct me if I'm wrong, but the "big ticket",
issue bytes/unicode filepaths, has been resolved. And looking at the
tracker, I only see 18 release blockers.
Well, if you mean that the resolution decided upon is to "simply
On Mon, Oct 6, 2008 at 7:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> So, we need to come up with a new release schedule for Python 3.0. My
> suggestion:
>
> 15-Oct-2008 3.0 beta 4
> 05-Nov-2008 3.0 rc 2
> 19-Nov-2008 3.0 rc 3
> 03-Dec-2008 3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, we need to come up with a new release schedule for Python 3.0. My
suggestion:
15-Oct-2008 3.0 beta 4
05-Nov-2008 3.0 rc 2
19-Nov-2008 3.0 rc 3
03-Dec-2008 3.0 final
Given what still needs to be done, is this a reasonable schedule? Do
we n
12 matches
Mail list logo
