I believe Collin is planning on doing a stand-alone release. But
having it in the 3.0a2 tarball makes sense so go ahead!
On Dec 5, 2007 9:54 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> For the upcoming release I like to add the 2to3 tools to the
> branches/py3k/Tools/ directory with an svn:e
For the upcoming release I like to add the 2to3 tools to the
branches/py3k/Tools/ directory with an svn:external property. Or do you
plan to release the 2to3 as standalone tool?
Christian
___
Python-3000 mailing list
[email protected]
http://mail.p
Jim Jewett schrieb:
> On 12/3/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> On Dec 3, 2007 12:12 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> > >> Sure. However, you could also use
>> > >> _testcapi.PY_SSIZE_T_MAX, or
>> > >> ctypes.sizeof(ctypes.py_object).
>
>> > > Much less intuitiv
I'm planning to freeze the py3k branch in 2-3 hours, some time
after/around 8pm PST (midnight UTC).
If someone wants to do another svnmerge from the trunk please do it
before then -- though we're nearly current so I don't mind not having
the last few changes merged into this release (it's only Ray
As Guido stated in a recent email, the stdlib reorg is going to be the
next big thing in Py3K-Land after a2 goes out the door. And since I
stuck my head out and wrote PEP 3108 and tried to spear-head a reorg
several times before, I am the de-facto junior dictator in charge of
the reorganization of
I've built and tested the latest py3k from scratch on Ubuntu, Fedora
7, OSX 10.4 and OSX 10.5, and found no issues.
So the code freeze is a fact. Don't check anything into the py3k
branch unless I tell you to. Please file high-priority bugs and assign
them to me if you think you've found a showsto
On Dec 5, 2007 11:14 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> So if this sounds interesting to you and you want to help me, let me know.
>
I am interested -- mainly in writing the import fixers and renaming
the modules.
-- Alexandre
___
Python-3000
