[Python-Dev] Move to a "py3k" branch *DONE*

[Guido van Rossum]

Please spread the word. The py3k-struni branch is dead! Don't use it any more.

--Guido

---------- Forwarded message ----------
From: Guido van Rossum <guido at python.org>
Date: Aug 9, 2007 7:43 AM
Subject: Move to a "py3k" branch *DONE*
To: Python 3000 <python-3000 at python.org>
Cc: Neal Norwitz <nnorwitz at gmail.com>


This is done. The new py3k branch is ready for business.

If you currently have the py3k-struni branch checked out (at its top
level), *don't update*, but issue the following commands:

  svn switch svn+ssh://pythondev@svn.python.org/python/branches/py3k
  svn update

Only a small amount of activity should result (unless you didn't svn
update for a long time).

For the p3yk branch, the same instructions will work, but the svn
update will update most of your tree. A "make clean" is recommended in
this case.

Left to do:

- update the wikis
- clean out the old branches
- switch the buildbot and the doc builder to use the new branch (Neal)

There are currently about 7 failing unit tests left:

test_bsddb
test_bsddb3
test_email
test_email_codecs
test_email_renamed
test_sqlite
test_urllib2_localnet

See http://wiki.python.org/moin/Py3kStrUniTests for detailed status
regarding these.

--Guido

On 8/9/07, Guido van Rossum <guido at python.org> wrote:
> I am starting now. Please, no more checkins to either p3yk ot py3k-struni.
>
> On 8/8/07, Guido van Rossum <guido at python.org> wrote:
> > I would like to move to a new branch soon for all Py3k development.
> >
> > I plan to name the branch "py3k".  It will be branched from
> > py3k-struni.  I will do one last set of merges from the trunk via p3yk
> > (note typo!) and py3k-struni, and then I will *delete* the old py3k
> > and py3k-struni branches (you will still be able to access their last
> > known good status by syncing back to a previous revision).  I will
> > temporarily shut up some unit tests to avoid getting endless spam from
> > Neal's buildbot.
> >
> > After the switch, you should be able to switch your workspaces to the
> > new branch using the "svn switch" command.
> >
> > If anyone is in the middle of something that would become painful due
> > to this changeover, let me know ASAP and I'll delay.
> >
> > I will send out another message when I start the move, and another
> > when I finish it.
> >
> > --
> > --Guido van Rossum (home page: http://www.python.org/~guido/)
> >
>
>
> --
> --Guido van Rossum (home page: http://www.python.org/~guido/)
>


--
--Guido van Rossum (home page: http://www.python.org/~guido/)


-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)