[Python-Dev] Migrating to subversion
I don't know whether anybody has done this before, but I just tried to run cvs2svn on the Python repository. The conversion took 7 hours, and the result is now available at http://www.dcl.hpi.uni-potsdam.de/python/branches/ Because of the load that the conversion produces on the machine, I cannot run the entire conversion every day. Reportedly, cvs2svn is able to run in incremental mode, but I haven't tried this out yet. On close inspection, you might notice a few things: - A few branches/tags are missing, namely r16b1|cnri-16-start|descr-branch|release152p1-patches|after-c all-reorg|r22a1|before-call-reorg|release16|r161|r161-branch|r16a2|release152p2 I had to manually exclude these tags, because cvs2svn complained that they (some of them) are tags on some files, and branches on other files. When I excluded these, it then complained that some other tags depend on the excluded ones, so I had to exclude these as well. I suspect that this can be fixed by modifying the CVS repository before the conversion, typically by converting the version tags to branch tags. cvs2svn did not report what files specifically caused the problems, and I don't know the proper cvs/rcs incantation to fix these. So if anybody has done that before, or knows how to, please let me know. - A few tags are useless, most notably the vendor branches. I think they should be excluded in the conversion. I don't know where the unlabeled branches come from, but they appear to be useless as well. - It has imported the CVSROOT directory as well. I don't know whether this is deliberate/useful. Anyway, this repository is now online for anonymous read-only access. Anybody interested in playing with it is welcome to do so. For those interested in server side issues: the repository is an 1.1.1 fsfs repository. The CVS repository consumes 368MiB; the SVN repository 797MiB. 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/archive%40mail-archive.com
Re: [Python-Dev] Migrating to subversion
On 06 March 2005, Martin v. Löwis said: - It has imported the CVSROOT directory as well. I don't know whether this is deliberate/useful. This is just an artifact of how SourceForge CVS repositories are organized. When I converted Optik's CVS to Subversion, I just did this: cvs2svn -s /home/svn/optik /home/cvs/optik/optik where /home/cvs/optik is what I got after unpacking the tarball downloaded from SF. Presumably for Python's repository, this would work: cvs2svn -s /home/svn/python /home/cvs/python/python ...except, umm, isn't distutils a separate top-level directory in the Python repository or something? That'll probably have to be fixed manually. Greg -- Greg Ward [EMAIL PROTECTED] http://www.gerg.ca/ The NSA. We care: we listen to our customers. ___ 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
Re: [Python-Dev] Documentation for __new__
I've LaTeX'ified the proposed documentation for __new__() and uploaded the patch to SF: http://sourceforge.net/tracker/download.php?group_id=5470atid=105470file_id=124422aid=1156412 Someone who really understands new-style classes should give this a look. (Guido?) I've tested that Python 2.3.5 and 2.4 (CVS) actually implement what's described in this doc patch, but it wouldn't hurt if someone read it from the point of view of what the promised constract is supposed to be! Greg -- Greg Ward [EMAIL PROTECTED] http://www.gerg.ca/ I'd like some JUNK FOOD ... and then I want to be ALONE -- ___ 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
[Python-Dev] Failing tests: marshal, warnings
Anyone else seeing test failures on the 2.4 branch right now? I started seeing this failure: test_warnings test test_warnings failed -- Traceback (most recent call last): File /scratch/src/python-2.4/Lib/test/test_warnings.py, line 57, in test_warn_specific_category warnings.warn(text, category) File /scratch/src/python-2.4/Lib/warnings.py, line 57, in warn warn_explicit(message, category, filename, lineno, module, registry) File /scratch/src/python-2.4/Lib/warnings.py, line 92, in warn_explicit raise message RuntimeWarning: unfiltered RuntimeWarning yesterday, so I cvs up'd today to see if it had been fixed. Now, not only is test_warnings failing, so is test_marshal: test_marshal test test_marshal failed -- Traceback (most recent call last): File /scratch/src/python-2.4/Lib/test/test_marshal.py, line 88, in test_floats got = marshal.load(file(test_support.TESTFN, rb)) IOError: [Errno 2] No such file or directory: '@test' Naturally, they only fail when running the full test suite. ;-( I sure hope my recent fix to textwrap isn't to blame! I'll fiddle around a bit in my working dir and see if I can figure out what's going on, but I'd like to know if I'm the only one seeing these problems... Greg -- Greg Ward [EMAIL PROTECTED] http://www.gerg.ca/ Never underestimate the power of human stupidity. ___ 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
Re: [Python-Dev] Failing tests: marshal, warnings
On 06 March 2005, I said: Anyone else seeing test failures on the 2.4 branch right now? I started seeing this failure: test_warnings test test_warnings failed -- Traceback (most recent call last): File /scratch/src/python-2.4/Lib/test/test_warnings.py, line 57, in test_warn_specific_category warnings.warn(text, category) File /scratch/src/python-2.4/Lib/warnings.py, line 57, in warn warn_explicit(message, category, filename, lineno, module, registry) File /scratch/src/python-2.4/Lib/warnings.py, line 92, in warn_explicit raise message RuntimeWarning: unfiltered RuntimeWarning [...] Naturally, they only fail when running the full test suite. OK, I've narrowed it down: test_warnings fails when run after test_descr: $ ./python -E Lib/test/regrtest.py test_descr test_warnings test_descr test_warnings test test_warnings failed -- Traceback (most recent call last): File /scratch/src/python-2.4/Lib/test/test_warnings.py, line 57, in test_warn_specific_category warnings.warn(text, category) File /scratch/src/python-2.4/Lib/warnings.py, line 57, in warn warn_explicit(message, category, filename, lineno, module, registry) File /scratch/src/python-2.4/Lib/warnings.py, line 92, in warn_explicit raise message RuntimeWarning: unfiltered RuntimeWarning Does this ring alarm bells with anyone? Greg -- Greg Ward [EMAIL PROTECTED] http://www.gerg.ca/ Gee, I feel kind of LIGHT in the head now, knowing I can't make my satellite dish PAYMENTS! ___ 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
Re: [Python-Dev] Failing tests: marshal, warnings
Greg Ward wrote: [SNIP] A-ha! I get it. There are two mistakes in test_descr.py:test_init(): lack of finally clause, and failure to make a copy of warnings.filters. This patch fixes both: --- Lib/test/test_descr.py 4 Mar 2005 04:47:04 - 1.202.2.2 +++ Lib/test/test_descr.py 7 Mar 2005 00:54:00 - @@ -3973,15 +3973,18 @@ def __init__(self): return 10 -oldfilters = warnings.filters -warnings.filterwarnings(error, category=RuntimeWarning) +oldfilters = warnings.filters[:] try: -Foo() -except RuntimeWarning: pass -else: -raise TestFailed, did not test __init__() for None return -warnings.filters = oldfilters +warnings.filterwarnings(error, category=RuntimeWarning) +try: +Foo() +except RuntimeWarning: +pass +else: +raise TestFailed, did not test __init__() for None return +finally: +warnings.filters = oldfilters def test_main(): I'll check this in and merge to the trunk once I see all tests passing. Well, I just checked in the list copy fix, so you only have to worry about adding the 'finally' clause to the 'try' statement. -Brett ___ 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
Re: [Python-Dev] Failing tests: marshal, warnings
Brett C. wrote: Greg Ward wrote: [SNIP] A-ha! I get it. There are two mistakes in test_descr.py:test_init(): lack of finally clause, and failure to make a copy of warnings.filters. This patch fixes both: --- Lib/test/test_descr.py 4 Mar 2005 04:47:04 - 1.202.2.2 +++ Lib/test/test_descr.py 7 Mar 2005 00:54:00 - @@ -3973,15 +3973,18 @@ def __init__(self): return 10 -oldfilters = warnings.filters -warnings.filterwarnings(error, category=RuntimeWarning) +oldfilters = warnings.filters[:] try: -Foo() -except RuntimeWarning: pass -else: -raise TestFailed, did not test __init__() for None return -warnings.filters = oldfilters +warnings.filterwarnings(error, category=RuntimeWarning) +try: +Foo() +except RuntimeWarning: +pass +else: +raise TestFailed, did not test __init__() for None return +finally: +warnings.filters = oldfilters def test_main(): I'll check this in and merge to the trunk once I see all tests passing. Well, I just checked in the list copy fix, so you only have to worry about adding the 'finally' clause to the 'try' statement. nm, the commit failed because Greg beat me to the checkin by like a second. -Brett ___ 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
Re: [Python-Dev] Failing tests: marshal, warnings
On 06 March 2005, I said: I'll check this in and merge to the trunk once I see all tests passing. Checked in on 2.4 branch. Not merged to trunk since Raymond hasn't merged his stuff to the trunk yet. Greg -- Greg Ward [EMAIL PROTECTED] http://www.gerg.ca/ I repeat myself when under stress I repeat myself when under stress I repeat--- ___ 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
Re: [Python-Dev] Useful thread project for 2.5?
[Phillip J. Eby] What would you suggest calling it? sys._current_frames(), returning a dictionary? I don't fight about names -- anything that doesn't make Guido puke works wink. I channel that sys._current_frames() would be fine. A dict mapping thread id to current thread frame would be lovely! ___ 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
[Python-Dev] Re: [Python-checkins] python/dist/src/Modules ossaudiodev.c, 1.35, 1.36
Greg, Um, unless I misread this, you added new attributes to the ossaudiodev objects in the 2.4 branch. Please don't do this - this is a new feature, and suddenly people who want to use those new attributes have to either test for version = 2.4.1, or else do a hasattr test. Please see the bugfix PEP for more rationale on this... Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ 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
