On 24/01/2011 23:14, "Martin v. Löwis" wrote:
This isn't a critical issue (nothing is broken) but we're a week
from another release candidate, so the new Py3.2 package
organization (unittest was flat in Py3.1 and its test were under
Lib/test) is about to become a de-facto decision that will be hard
to undo.
Well can we stop being melodramatic? Tests are not part of the API
and so they are free to move whenever we want. No need to hold a
release candidate for that.
Of course there is. Any addition or removal of files at this point has
the chance of breaking the release process, which may fail to pick up
files, or break in trying to pick up files that it expected to be there.
This has happened *many* times during the alpha and beta releases of
3.2, so it's not at all a theoretical problem.
After the next release candidate, I'd prefer to see no changes
whatsoever to the tree (but it's Georg's decision, of course).
What Antoine meant is that we could make the change for 3.2.1 and don't
need to delay 3.2.
Michael
Regards,
Martin
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
--
http://www.voidspace.org.uk/
May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing http://www.sqlite.org/different.html
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
