Mailman 3 January 2002 - Python-Dev

Re: [Python-Dev] unicode/string asymmetries
by Jack Jansen 11 Jan '02

11 Jan '02

Recently, "Martin v. Loewis" <martin(a)v.loewis.de> said: > > One minor misgiving is that this call will *always* copy the string, > > even if the internal coding of unicode objects is wchar_t. That's a > > bit of a nuisance, but we can try to fix that later. > > Not sure what you mean by "later". Once this is being used, you cannot > fix it anymore. By "later" I meant "when your argtuple idea has been accepted":-) Remember: most of my code is generated anyway, so fixing things like this is a minor effort. In case it wasn't clear yet: this is a firm +1 for the argtuple idea. -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

1 0

Ouch -- CVS troubles with 2.1.2c1
by Tim Peters 11 Jan '02

11 Jan '02

Trying to add a new file to the release21-maint branch caused CVS commit to die with an assertion error: C:\Code\python\dist\src\PCbuild>cvs commit uninstal.wse RCS file: /cvsroot/python/python/dist/src/PCbuild/Attic/uninstal.wse,v done cvs: commit.c:2104: checkaddfile: Assertion `*rcsnode == ((void *)0)' failed. Terminated with fatal signal 6 CVS.EXE commit: saving log message in c:\windows\TEMP\3 Trying again finds a stale lock: C:\Code\python\dist\src\PCbuild>cvs commit uninstal.wse cvs server: [12:22:36] waiting for tim_one's lock in /cvsroot/python/python/dist/src/PCbuild cvs server: [12:23:06] waiting for tim_one's lock in /cvsroot/python/python/dist/src/PCbuild ... Anyone got a clue?

3 3

2.1.2 release -- do we need a beta?
by Guido van Rossum 10 Jan '02

10 Jan '02

Do we need a beta for the 2.1.2 release? I think it might be prudent -- Anthony's last-minute checking of a critical fix to a bug that prevented compilation on one platform points this out again. The alternative is to be optimistic, and to quickly release 2.1.3 if 2.1.2 has a problem that we discover after its release. Opinions? I think a beta is prudent, and it shouldn't cost too much more in effort -- if we're lucky, nothing changes and we just fiddle some version numbers. If it turns out to be needed, it's better than having to wear a brown bag over your head. :-) --Guido van Rossum (home page: http://www.python.org/~guido/)

4 4

Re: [Zope.Com Geeks] 2.1.2 testing.
by Anthony Baxter 10 Jan '02

10 Jan '02

Jens tested MacOS X. Results below: >>> Jens Vagelpohl wrote > anthony, > > here is what i found: > > as a "basic" build with the minimum configure options required to compile > (--with-dyld --with-suffix) i get the following test results (after upping > the stacksize to allow the re and sre-tests to succeed): > > 119 tests OK. > 1 test failed: test_largefile > 20 tests skipped: test_al test_cd test_cl test_dl test_fcntl test_gdbm > test_gl test_imgfile test_linuxaudiodev test_locale test_minidom test_nis > test_poll test_pty test_pyexpat test_sax test_socketserver > test_sunaudiodev test_winreg test_winsound > make: *** [test] Error 1 > > this is the same result as with 2.1.1. then, as a last test, i built and > tested zope with it. all unit tests run except for 3 ZODB tests which are > most likely not due to python misbehaving. > > lookin' good! > > jens > -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

1 0

Python 2.1.2c1 docs
by Fred L. Drake, Jr. 10 Jan '02

10 Jan '02

The documentation for Python 2.1.2c1 is online at: http://python.sourceforge.net/maint21-docs/ Please report any real problems with these docs to me or Anthony with a level 7 priority and set the "Group" to "Python 2.1.2". To file a bug, log into SourceForge and then visit: http://sourceforge.net/tracker/index.php?group_id=5470&atid=105470 Thanks! -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation

1 0

Re: [Python-Dev] 2.1.2 release -- do we need a beta?
by Anthony Baxter 10 Jan '02

10 Jan '02

>>> Guido van Rossum wrote > [Anthony] > > Ok. In that case I'll put the version back to rc1, and will start rolling > > the tarball? > > > > (Not going to do it immediately - but soonish...) > > But how about the Windows installer? A release isn't done without it. That, I can't help you with. I don't have access to MSVC, and I don't have the requisite level of windows knowledge to do the build, anyway. (PEP-0101 refers to 'Windows Magic'. What's Tim's time like? Anthony -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

1 0

Re: [Python-Dev] 2.1.2 testing.
by Fred L. Drake, Jr. 10 Jan '02

10 Jan '02

[Sending to python-dev so people know the results for Solaris 2.8.] Anthony Baxter writes: > > I'm exporting onto Solaris 2.8 now; will report the results. > > Great. If you get a chance to try it with some non-standard build > args, that would also be appreciated... Specific suggestions please! I've not looked at those in a while, so I don't know which would be most useful. A note summarizing desired alternate builds would be good. Results for Solaris 2.8, gcc 2.95.2: 117 tests OK. 1 test failed: test_sunaudiodev 22 tests skipped: test_al test_bsddb test_cd test_cl test_dl test_gdbm test_gl test_gzip test_imgfile test_largefile test_linuxaudiodev test_minidom test_nis test_openpty test_pyexpat test_sax test_socketserver test_sundry test_winreg test_winsound test_zipfile test_zlib The sunaudiodev failure is "permission denied", which is not a real failure; treat this as skipped. (The machine is not local to me, so there's no way for me to know if the test worked anyway.) Note that many of the optional modules don't get built on that machine, but I can't do much (and nothing quickly) to change the availability of additional libraries. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation

1 0

Re: 2.1.2 release -- do we need a beta?
by Anthony Baxter 10 Jan '02

10 Jan '02

>>> Guido van Rossum wrote > Do we need a beta for the 2.1.2 release? I think it might be prudent > -- Anthony's last-minute checking of a critical fix to a bug that > prevented compilation on one platform points this out again. Maybe. But on the other hand, I've also done a bunch of different builds on as many platforms as I could find. [The oopsie I found was actually probably the most complex merge of the lot, and that's not saying much. put it down to too many CVS checkouts and not enough brain :)] The ugliness potential is from either those platforms that are an offense against nature that no-one thinks to try, or from some sort of weird compilation options. I don't think that there's many of the fixes in the 2.1.2 code that are going to break something that worked before - with the list of platforms I've hit tonight, I think I've got most of the new code exercised. (One of the minor-ish constraints I put on candidate fixes was whether or not I could easily test it.) The other question I have to ask is whether people will actually download and test a beta/release candidate of a bugfix release. Anthony -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

2 1

2.1.2 build on Mandrake
by Skip Montanaro 10 Jan '02

10 Jan '02

I got the usual output on my Mandrake 8.1 system when building the release21-maint branch: 126 tests OK. 1 test failed: test_linuxaudiodev 13 tests skipped: test_al test_cd test_cl test_dbm test_dl test_gl test_imgfile test_largefile test_nis test_socketserver test_sunaudiodev test_winreg test_winsound Skip

1 0

Re: [Python-Dev] 2.1.2 testing.
by Anthony Baxter 10 Jan '02

10 Jan '02

It's still release21-maint. I'm waiting til I've finished my testing before making the tag. (As it's a bugfix release, I'm not making a release branch off the existing maintenance branch (that path leads to madness)) Ta, Anthony >>> "Skip Montanaro" wrote > > Anthony> Has anyone had a chance to test that 2.1.2 builds and works > Anthony> correctly on anything? > > I will give it a quick try on my Mandrake 8.1 system. What's the relevant > CVS branch? I didn't see anything obvious like "r212". > > Skip > -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

1 0