Re: [Python-Dev] Upcoming 2.5.2 release
It would be very nice if http://bugs.python.org/issue1692335 fix was included in 2.5.2. The patch exists, have been tested, reviewed by Georg Brandl, who says he needs some other developer to review the patches (there is a separate patch for 2.6). Could please someone look at the issue and help get the problem fixed in 2.5.2.? Regards, Jaroslav Pachola ___ 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] Tracker marks my messages as spam :-)
Perhaps it has to do with the low signal to noise ratio of your messages... Nicko On 31 Jan 2008, at 10:07, Jesus Cea wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > This will be my last email today, I don't want to waste (more of) your *valuable* time. > > http://bugs.python.org/issue1391 > http://bugs.python.org/msg61892 > > - -- > Jesus Cea Avion _/_/ _/_/_/_/_/_/ > [EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/_/_/ _/_/_/_/ _/ > _/ > jabber / xmpp:[EMAIL PROTECTED] _/_/_/_/ _/_/_/_/_/ > ~ _/_/ _/_/_/_/ _/_/ _/_/ > "Things are not so easy" _/_/ _/_/_/_/ _/_/_/_/ _/_/ > "My name is Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ > "El amor es poner tu felicidad en la felicidad de otro" - Leibniz > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iQCVAwUBR6Gd25lgi5GaxT1NAQLDiwP/aMUOxhoRH8/ZnCtHCUzr95tIJUe1ySh6 > SuDjR3OS19S8lcRVgEL0droIP44lmozpdyOW1eaPDPBMA02XCqiPWmCxBCeXsbJ/ > xf/XVzl53vAQmtfqxHrNyrS+mXv5YW2CjOKWk52IKuf/Rckf9FYSP13OKW7WTjNy > orjAdOYRd/8= > =gSNB > -END PGP SIGNATURE- > ___ > 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/nicko%40nicko.org ___ 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] Upcoming 2.5.2 release
On 1/31/08, Christian Heimes <[EMAIL PROTECTED]> wrote: > > Jesus Cea wrote: > > My guess is that 2.5 branch is still open to more patches than pure > > security/stability patches, so "backporting" BerkeleyDB 4.6 support > > seems reasonable (to me). If I'm wrong, please educate me :-). > > I think you are wrong, sorry pal! DB 4.6 support is a new feature. New > features must land in the development version(s) of Python, that is > Python 2.6 and 3.0. You must change as less code as possible in Python > 2.5 to fix a severe problem. > > Christian > Actually in all past releaseXX-maint branches I have merged in support for compiling against a new version of BerkeleyDB. Its not a feature, its just something you have to do to support compiling against a new library version. Why is this ok? * There are no API changes on the python module side. * Binary releases of python for windows continue to be compiled against the same BerkeleyDB version that was used in the 2.5.0 release. the combo of those two things keeps it sane to do this. As Martin pointed out, I already merged that trivial change in to release25-maint a while back. That said, BerkeleyDB 4.6.x has proven to be a bit of an unstable release from Oracle so I'm considering modifying setup.py to disable linking against that version by default. I'll be reviewing buildbot results this weekend. As already mentioned by Neal i've disabled 4.6 support in trunk to watch the buildbots. I'll go over the results this weekend to make a decision on whether or not python's setup.py should default to allowing itself to link against 4.6.x or not in hopes of avoiding people filing bugs against us for what is ultimately Oracle's problem. -Greg ___ 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] Summary of Tracker Issues
ACTIVITY SUMMARY (01/25/08 - 02/01/08) Tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 1680 open (+31) / 12172 closed (+21) / 13852 total (+52) Open issues with patches: 434 Average duration of open issues: 759 days. Median duration of open issues: 1045 days. Open Issues Breakdown open 1656 (+30) pending24 ( +1) Issues Created Or Reopened (52) ___ os.path.isabs documentation error01/25/08 CLOSED http://bugs.python.org/issue1933created giampaolo.rodola os.path.isabs documentation error01/25/08 CLOSED http://bugs.python.org/issue1934created giampaolo.rodola test_descr.py converted to unittest 01/25/08 http://bugs.python.org/issue1935created amaury.forgeotdarc patch test_zipfile failure 01/26/08 CLOSED http://bugs.python.org/issue1938created giampaolo.rodola code object docstring obsolete 01/26/08 CLOSED http://bugs.python.org/issue1939created pitrou curses.filter can not be used as described in its documentation 01/26/08 CLOSED http://bugs.python.org/issue1940created robinbryce 2.6 stdlib using with statement 01/26/08 http://bugs.python.org/issue1941created gutworth patch test_plistlib started failing01/26/08 CLOSED http://bugs.python.org/issue1942created gvanrossum improved allocation of PyUnicode objects 01/26/08 http://bugs.python.org/issue1943created pitrou Documentation for PyUnicode_AsString (et al.) missing. 01/27/08 http://bugs.python.org/issue1944created alexandre.vassalotti easy Document back ported C functions 01/27/08 http://bugs.python.org/issue1945created tiran easy re.search hangs on this 01/27/08 http://bugs.python.org/issue1946created itsadok Exception exceptions.AttributeError '_shutdown' in http://bugs.python.org/issue1947created Mr Shore Cant open python gui using VISTA 01/27/08 http://bugs.python.org/issue1948created needhelpasap test_ntpath.py converted to unittest 01/27/08 http://bugs.python.org/issue1949created giampaolo.rodola patch, easy Potential overflows due to incorrect usage of PyUnicode_AsString 01/27/08 http://bugs.python.org/issue1950created alexandre.vassalotti patch test_wave.py converted to unittest 01/28/08 http://bugs.python.org/issue1951created giampaolo.rodola patch, easy test_select.py converted to unittest 01/28/08 http://bugs.python.org/issue1952created giampaolo.rodola patch Compact int and float freelists 01/28/08 http://bugs.python.org/issue1953created tiran patch SocketServer.ForkingMixIn creates a zombie 01/28/08 CLOSED http://bugs.python.or
Re: [Python-Dev] Tracker marks my messages as spam :-)
On Feb 1, 2008 6:43 AM, Nicko van Someren <[EMAIL PROTECTED]> wrote: > Perhaps it has to do with the low signal to noise ratio of your > messages... That was a little uncalled for. Be polite. ___ 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] Tracker marks my messages as spam :-)
Jeffrey Yasskin wrote: > On Feb 1, 2008 6:43 AM, Nicko van Someren <[EMAIL PROTECTED]> wrote: >> Perhaps it has to do with the low signal to noise ratio of your >> messages... > > That was a little uncalled for. Be polite. I don't believe it was at all impolite: It was a literal observation of a relevant phenomenon. Jesus's email that started this thread used 1305 characters to simply say "This will be my last email today, I don't want to waste (more of) your *valuable* time." a message of 89 characters. By anyone's standards that's a low S/N ratio. Even without the digital signature overhead it is still 89 characters from a total of 648 ... it's quite possible that's why his messages are being misinterpreted. regards Steve -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ ___ 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] Tracker marks my messages as spam :-)
No. The message Jesus added to the tracer was, in its entirety: """ Oracle confirms the issue. They will provide a patch. """ That's just small, but has a high S/N ratio. The contents of Jesus' email has nothing to do with this issue. On Feb 1, 2008 10:37 AM, Steve Holden <[EMAIL PROTECTED]> wrote: > Jeffrey Yasskin wrote: > > On Feb 1, 2008 6:43 AM, Nicko van Someren <[EMAIL PROTECTED]> wrote: > >> Perhaps it has to do with the low signal to noise ratio of your > >> messages... > > > > That was a little uncalled for. Be polite. > > I don't believe it was at all impolite: It was a literal observation of > a relevant phenomenon. Jesus's email that started this thread used 1305 > characters to simply say > > "This will be my last email today, I don't want to waste (more of) your > *valuable* time." > > a message of 89 characters. By anyone's standards that's a low S/N > ratio. Even without the digital signature overhead it is still 89 > characters from a total of 648 ... it's quite possible that's why his > messages are being misinterpreted. > > regards > Steve > -- > Steve Holden+1 571 484 6266 +1 800 494 3119 > Holden Web LLC http://www.holdenweb.com/ > > > ___ > 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/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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] Tracker marks my messages as spam :-)
On 1 Feb 2008, at 18:37, Steve Holden wrote: > Jeffrey Yasskin wrote: >> On Feb 1, 2008 6:43 AM, Nicko van Someren <[EMAIL PROTECTED]> wrote: >>> Perhaps it has to do with the low signal to noise ratio of your >>> messages... >> >> That was a little uncalled for. Be polite. > > I don't believe it was at all impolite: It was a literal observation > of > a relevant phenomenon. Jesus's email that started this thread used > 1305 > characters to simply say > > "This will be my last email today, I don't want to waste (more of) > your > *valuable* time." > > a message of 89 characters. By anyone's standards that's a low S/N > ratio. Even without the digital signature overhead it is still 89 > characters from a total of 648 ... it's quite possible that's why his > messages are being misinterpreted. Exactly. I by no means meant to suggest that the quality of the content was low, only that it was lost in a morass of padding which might confuse a spam filter. Sorry if my comment was misconstrued. Nicko ___ 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] Python on non IEEE-754 platforms: plea for information.
A request for information: What non IEEE 754 platforms exist that people care about running Python 2.6, Python 3.0 and higher on? By non IEEE 754 platform, I mean a platform where either the C double is not the usual 64-bit IEEE floating-point format, or where the C double is IEEE format but the platform deviates in major ways from the IEEE 754 specification. There are a few places (mostly in mathmodule.c, cmathmodule.c, floatobject.c, longobject.c) where it's not clear that the code behaves correctly on non-IEEE platforms, and I'm finding it difficult to determine how broken (or not) it is without having a clear idea of what possible unusual floating-point formats might come up. The major non-IEEE floating-point formats that I know of, on big iron, are the VAX, Cray and IBM formats; I believe anything else is too old to worry about. Is this true? The IBM format is particularly troublesome because it's base 16 instead of base 2 (so e.g. multiplying a float by 2 can lose bits), but it appears that recent IBM machines do both IBM format and IEEE format floating-point. I assume that the S-390 buildbots are using the IEEE side---is this true? At the other end of the spectrum are embedded devices and cellphones. Here I have no idea what the situation is at all---any information would be valuable. Mark ___ 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] Python on non IEEE-754 platforms: plea for information.
Mark Dickinson wrote: > At the other end of the spectrum are embedded devices and cellphones. Here > I have no idea what the situation is at all---any information would be > valuable. I know two mobile phone platforms for Python: Nokia S60 and Pippy for Palm. I haven't had time to study Python on Nokia S60 Series yet. Palm's hardware and Pippy don't support floats at all. Pippy Python is an old 1.5 (?) without the float type. The third major platform and last platform for mobile devices I can think for right now are Qtopia and WinCE. I haven't dealt with them either so you've to check the specs. Python on Nokia S60 Series: (Python 2.2.x) http://www.forum.nokia.com/info/sw.nokia.com/id/ee447e84-2851-471a-8387-3434345f2eb0/Python_for_S60.html http://wiki.opensource.nokia.com/projects/Python_for_S60 Pippy: http://pippy.sourceforge.net/ Qtopia: http://en.wikipedia.org/wiki/Qtopia http://www.trolltech.com/products/qtopia/ WinCE: http://en.wikipedia.org/wiki/WinCE Christian ___ 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] Python on non IEEE-754 platforms: plea for information.
> What non IEEE 754 platforms exist that people care about running Python > 2.6, Python 3.0 and higher on? VMS, that's even supported to some degree in the source tree, and OS/390 (aka z/OS); patches to support it have been rejected, but people will likely maintain a fork themselves. > The major non-IEEE floating-point formats that I know of, on big iron, > are the VAX, Cray and IBM formats; I believe anything else is too old > to worry about. Is this true? Mostly. For VAX, there exist two double formats: the D format, and the G format - not sure whether you counted them as two. > The IBM format is particularly > troublesome because it's base 16 instead of base 2 (so e.g. multiplying > a float by 2 can lose bits), but it appears that recent IBM machines do > both IBM format and IEEE format floating-point. I assume that the S-390 > buildbots are using the IEEE side---is this true? They run Linux, so yes. Notice that other people also run Python on z/OS. 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] Python on non IEEE-754 platforms: plea for information.
Mark Dickinson wrote: > At the other end of the spectrum are embedded devices and cellphones. Here > I have no idea what the situation is at all---any information would be > valuable. I spoke to Mikko Ohtamaa (Moo-- on #pys60) and he gave me the name of a Nokia developer and this link http://discussion.forum.nokia.com/forum/showthread.php?t=97263. I already contacted the developer and asked him to reply here. Christian ___ 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] Python on non IEEE-754 platforms: plea for information.
On Feb 1, 2008 7:56 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > Mostly. For VAX, there exist two double formats: the D format, and the > G format - not sure whether you counted them as two. > I didn't. Thanks. > They run Linux, so yes. Notice that other people also run Python on z/OS. > Okay. So FLT_RADIX==2 can't be assumed, in general. Thanks for the information. Mark ___ 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] Python on non IEEE-754 platforms: plea for information.
On Feb 1, 2008 2:52 PM, Mark Dickinson <[EMAIL PROTECTED]> wrote: > The IBM format is particularly troublesome because > it's base 16 instead of base 2 (so e.g. multiplying a float by 2 can lose > bits), but it appears that recent IBM machines do both IBM format and IEEE > format floating-point. I assume that the S-390 buildbots are using the IEEE > side---is this true? I don't know and suspect the only way to figure it out would be to write a test that would expose which is being used. It's using gcc, so we probably get whatever the compiler defaults to. Sometimes we have to specify flags for certain platforms. For example -mieee on the Alpha. It's fine to check in something so that you can get an answer on a buildbot. n ___ 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] Python on non IEEE-754 platforms: plea for information.
On Feb 1, 2008 8:04 PM, Christian Heimes <[EMAIL PROTECTED]> wrote: > I spoke to Mikko Ohtamaa (Moo-- on #pys60) and he gave me the name of a > Nokia developer and this link > http://discussion.forum.nokia.com/forum/showthread.php?t=97263. I > already contacted the developer and asked him to reply here. > Thank you: a very useful thread. From what little information I'm turning up on Google, it looks as though most of these devices---if they support floating-point at all---provide some reasonably close approximation to IEEE 754 floats (possibly emulated in software). ___ 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] Python on non IEEE-754 platforms: plea for information.
On Feb 1, 2008 6:31 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > On Feb 1, 2008 2:52 PM, Mark Dickinson <[EMAIL PROTECTED]> wrote: > > The IBM format is particularly troublesome because > > it's base 16 instead of base 2 (so e.g. multiplying a float by 2 can lose > > bits), but it appears that recent IBM machines do both IBM format and IEEE > > format floating-point. I assume that the S-390 buildbots are using the IEEE > > side---is this true? > > I don't know and suspect the only way to figure it out would be to > write a test that would expose which is being used. It's using gcc, > so we probably get whatever the compiler defaults to. Sometimes we > have to specify flags for certain platforms. For example -mieee on > the Alpha. > > It's fine to check in something so that you can get an answer on a buildbot. Actually, an even better way to do this would be to craft a test case that exposes the assumptions you've found about the floating format. Then it'll be a valuable regression test even after someone fixes the bug. -- Namasté, Jeffrey Yasskin ___ 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] Tracker marks my messages as spam :-)
Guido> """ Guido> Oracle confirms the issue. They will provide a patch. Guido> """ Guido> That's just small, but has a high S/N ratio. The contents of Jesus' Guido> email has nothing to do with this issue. As Martin pointed out, small messages tend to get classified as either spam or unsure. The spam filter built into the Roundup instance uses the SpamBayes classifier. I don't know how many examples have been trained so far, but I would guess very few. It's unlikely that the small message gave any useful clues (far enough away from a score of 0.5 in either the spam or ham directions) to the classifier. Maybe "Oracle" or "patch" would have been hammy clues. The others were probably tossed out. In short, there just wasn't enough "meat" to chew on. Of course, without seeing the classifier's database and input it's kind of hard to be more precise. Over time though, even such short messages should be classified more accurately as the training database grows. Skip ___ 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
