Re: [Python-Dev] test_quopri, test_wait3, and test_popen2
Neal Norwitz wrote: > I played with this some last night and found the same ordering. I > have a different patch that also fixes the problem. It also fixes 2-3 > bugs I think. Basically the child could be waited on from outside > popen (or from 2 threads). The question is what should we do if that > happens? As discussed in the patch: If the application calls wait() at some point, or poll() (in the same thread or a different thread), then it is correct if .wait() will raise an os.error (ECHILD) - the pid was already waited on. OTOH, _cleanup shouldn't mess with pids that the application still might want to wait on; _cleanup should also clean out objects that already have been waited on. So my proposal is that Popen3 objects should be added to _active only in __del__. 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] test_quopri, test_wait3, and test_popen2
On 3/23/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > I have been looking into the (seemingly random) test_popen2 > failures today, and found that it fails when the tests I played with this some last night and found the same ordering. I have a different patch that also fixes the problem. It also fixes 2-3 bugs I think. Basically the child could be waited on from outside popen (or from 2 threads). The question is what should we do if that happens? I wrapped some calls and handled the exceptions. Threads can be handled fine since we have the return result. But if the child was waited on from outside popen, we don't have the status info. I'm not sure what to do about that. There is a problem with the patch that I should use self.sts if it's not -1. See bug #1183780 for the details. 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
Nick Coghlan wrote: > +1 on simply changing the messages to python-checkins instead of here - it > gives the build failure better context than it gets on python-dev, and > subscribing to python-checkins is a fair indication of willingness to receive > frequent automated mail ;) Ok, I changed the address to python-checkins. It might take some delay initially, because messages will have to be approved by a list moderator. 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
[Python-Dev] test_quopri, test_wait3, and test_popen2
I have been looking into the (seemingly random) test_popen2 failures today, and found that it fails when the tests are run in the order given in the subject. Here is what happens: - test_quopri uses os.popen2, which in turn creates a popen2.Popen3 object. It processes stdin/stdout, but never calls wait on that the process (it can't: os.popen2 doesn't return the pid). This is a flaw (the process should be waited for) which I fixed. - test_wait3 has a loop to wait for child processes, which invokes wait repeatedly until the expected child pid is returned. In the process, it might receive the wait status from processes it didn't start. This is a flaw which I didn't address - I wonder why there is a loop, instead of just waiting once, and expecting the PID of the process that had been created just before. - test_popen2 invokes _cleanup at the end, which waits for all _active processes. Now, since test_quopri added an active process, and test_wait3 deleted its pid, _cleanup fails with the error that the pid is no longer valid. I made that failure more obvious. So here is what I did to address these: - I changed test_quopri to use subprocess.Popen().communicate() to invoke quopri as a program. communicate will wait() for the child process. - I changed test_popen2 to check at the beginning that there are no active processes. To print out the commands that are still active, I added the cmd string to the Popen objects. It turned out that this broke the Windows builds, which, in turn, resolves as a hidden bug/feature of quopri command line mode. When "python -mquopri http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt
M.-A. Lemburg wrote: > That would be Donn Cave: > > http://bebits.com/app/4232 > > He's also the one who wrote the Bethon wrapper for the BeOS C++ API. > > BTW, the fact that you don't see new checkins doesn't necessarily > mean that a port is no longer used. It may just be that the existing > port still works without changes. From that page: "Includes Bethon 0.5.3 libraries, and patches to build Python 2.4.2 from source." So it looks like the patches are not being contributed back. OTOH, looking at the patches, some of them might not be suitable for inclusion, anyway (but some are, of course). 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
[Python-Dev] Patch to add timestamp() method to datetime objects
Hi, I've just submitted patch #1457227 which adds a convenience method to datetime objects to get the timestamp. It's equivalent to time.mktime(d.timetuple()), I just wanted to save myself some typing and be able to write d.timestamp() instead. I hope I have the dst code right. Would d.utctimestamp() be useful as well? Cheers, Chris ___ 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] r43214 - peps/trunk/pep-3000.txt
On 3/23/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > Martin v. Löwis wrote: > > M.-A. Lemburg wrote: > >>> And we still have someone actively interested in maintaining the OS2 > >>> port, it seems. > >> > >> Dito for BeOS, now under the name Zeta OS. > > > > Who is the one interested in maintaining the BeOS port? the last > > checkins related to BeOS seem to originate from the 2001/2002 period. > > That would be Donn Cave: > > http://bebits.com/app/4232 > > He's also the one who wrote the Bethon wrapper for the BeOS C++ API. > > BTW, the fact that you don't see new checkins doesn't necessarily > mean that a port is no longer used. It may just be that the existing > port still works without changes. True, but note that he says there are patches against 2.4.2. So he apparently is maintaining this outside the Python source tree. If that's already the case, is it worth us keeping all the #ifdef'ery etc in the trunk? I know Donn from his c.l.p postings, but I don't recall him on python-dev or seeing a patch. Donn if you are here, care to explain what direction you think we should take? 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
[Python-Dev] buildbot warnings in x86 XP-2 trunk
The Buildbot has detected a new failure of x86 XP-2 trunk. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20XP-2%20trunk/builds/96 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: hyeshik.chang,martin.v.loewis Build Had Warnings: warnings test sincerely, -The Buildbot ___ 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] buildbot warnings in x86 XP trunk
The Buildbot has detected a new failure of x86 XP trunk. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20XP%20trunk/builds/120 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: martin.v.loewis Build Had Warnings: warnings test sincerely, -The Buildbot ___ 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] buildbot warnings in x86 W2k trunk
The Buildbot has detected a new failure of x86 W2k trunk. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20W2k%20trunk/builds/122 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: martin.v.loewis Build Had Warnings: warnings test sincerely, -The Buildbot ___ 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
On Thu, Mar 23, 2006, Nick Coghlan wrote: > > +1 on simply changing the messages to python-checkins instead of > here - it gives the build failure better context than it gets on > python-dev, and subscribing to python-checkins is a fair indication of > willingness to receive frequent automated mail ;) +1 python-checkins -- I'm not subscribed to python-checkins, and the buildbot messages mean nothing to me. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "19. A language that doesn't affect the way you think about programming, is not worth knowing." --Alan Perlis ___ 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] buildbot warnings in sparc solaris10 gcc trunk
The Buildbot has detected a new failure of sparc solaris10 gcc trunk. Full details are available at: http://www.python.org/dev/buildbot/all/sparc%20solaris10%20gcc%20trunk/builds/113 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: hyeshik.chang Build Had Warnings: warnings test sincerely, -The Buildbot ___ 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] release24-maint unfrozen, kinda
2.4.3c1 is out, so the release24-maint branch is kinda unfrozen. I want to cut a 2.4.3 final next week, so please be very very cautious about checkins to the branch. A 2.4.4 will follow sometime in 6 months, or after 2.5 final is out, whichever is sooner. -- 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
[Python-Dev] buildbot warnings in x86 gentoo trunk
The Buildbot has detected a new failure of x86 gentoo trunk. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20gentoo%20trunk/builds/119 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: hyeshik.chang Build Had Warnings: warnings test sincerely, -The Buildbot ___ 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] RELEASED Python 2.4.3, release candidate 1
On behalf of the Python development team and the Python community, I'm happy to announce the release of Python 2.4.3 (release candidate 1). Python 2.4.3 is a bug-fix release. See the release notes at the website (also available as Misc/NEWS in the source distribution) for details of the more than 50 bugs squished in this release, including a number found by the Coverity Scan project. Assuming no major problems crop up, a final release of Python 2.4.3 will follow in about a week's time. For more information on Python 2.4.3, including download links for various platforms, release notes, and known issues, please see: http://www.python.org/2.4.3/ Highlights of this new release include: - Bug fixes. According to the release notes, at least 50 have been fixed since 2.4.2. Highlights of the previous major Python release (2.4) are available from the Python 2.4 page, at http://www.python.org/2.4/highlights.html On a personal note, according to my records this is the 25th release of Python I've made as release manager. So enjoy this silver anniversary release, Anthony Anthony Baxter [EMAIL PROTECTED] Python Release Manager (on behalf of the entire python-dev team) ___ 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] r43214 - peps/trunk/pep-3000.txt
Martin v. Löwis wrote: > M.-A. Lemburg wrote: >>> And we still have someone actively interested in maintaining the OS2 >>> port, it seems. >> >> Dito for BeOS, now under the name Zeta OS. > > Who is the one interested in maintaining the BeOS port? the last > checkins related to BeOS seem to originate from the 2001/2002 period. That would be Donn Cave: http://bebits.com/app/4232 He's also the one who wrote the Bethon wrapper for the BeOS C++ API. BTW, the fact that you don't see new checkins doesn't necessarily mean that a port is no longer used. It may just be that the existing port still works without changes. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 23 2006) >>> Python/Zope Consulting and Support ...http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ___ 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
Neal Norwitz wrote: > On 3/22/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: >> M.-A. Lemburg wrote: >>> For the Snake-Farm we had a separate mailing list, so I'd prefer >>> that if possible. This lets you opt-in to the messages and also >>> makes it easier to search via the python.org search facility. >> I'll wait for other people to voice an opinion. Creating a new >> mailing list is an effort I'd like to avoid. > > Hopefully we will get it tuned better soon so there aren't so many > mails. Unfortunately, it may take a while due to the ssize_t issues > getting fixed as we find them. > > I'd be happy if the messages were on python-checkins. +1 on simply changing the messages to python-checkins instead of here - it gives the build failure better context than it gets on python-dev, and subscribing to python-checkins is a fair indication of willingness to receive frequent automated mail ;) Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.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] Building Python for AMD64 (Windows)
Trent Mick wrote: > [Thomas Heller wrote] >> Linking... >>Creating library .\./python25.lib and object .\./python25.exp >> zipimport.obj : error LNK2001: unresolved external symbol __security_cookie >> traceback.obj : error LNK2001: unresolved external symbol __security_cookie >> typeobject.obj : error LNK2001: unresolved external symbol __security_cookie >> unicodeobject.obj : error LNK2001: unresolved external symbol >> __security_cookie >> >> (lots of similar errors...) > > I have this patch to the python 2.4 sources to get win64-ia64 to build > (that I haven't yet had the chance to submit to SF). I think it will > require a little massaging for the trunk. Does this work for you? Yes, I was able to compile pythoncore when I added bufferoverflowU.lib to the project. However, starting python.exe immediately crashes with an access violation, in sys_getwindowsversion, in the PyBuild_Value() call. Thomas ___ 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
