Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt
neal.norwitz wrote: > +Outstanding Issues > +== > + > +* Require C99, so we can use // comments, named initializers, declare > variables > + without introducing a new scope, among other benefits. gcc only, in other words ? > +* Remove support for old systems, including: OS2, BeOS, RISCOS, (SGI) Irix, > Tru64 what's old with tru64 ? it's not that uncommon in places where Python has a strong presence, you can still buy AXP hardware throughout 2006, and HP says they'll keep developing and supporting the software platform at least through 2011. ___ 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
"Fredrik Lundh" <[EMAIL PROTECTED]> writes: > neal.norwitz wrote: > >> +Outstanding Issues >> +== >> + >> +* Require C99, so we can use // comments, named initializers, declare >> variables >> + without introducing a new scope, among other benefits. > > gcc only, in other words ? Heh, I was going to make this point as well: it's not clear that MSVC will ever support C99. It supports some of the features listed here, of course, but probably won't support everything. >> +* Remove support for old systems, including: OS2, BeOS, RISCOS, (SGI) Irix, >> Tru64 > > what's old with tru64 ? it's not that uncommon in places where Python > has a strong presence, you can still buy AXP hardware throughout 2006, > and HP says they'll keep developing and supporting the software platform > at least through 2011. And we still have someone actively interested in maintaining the OS2 port, it seems. Cheers, mwh -- I never disputed the Perl hacking skill of the Slashdot creators. My objections are to the editors' taste, the site's ugly visual design, and the Slashdot community's raging stupidity. -- http://www.cs.washington.edu/homes/klee/misc/slashdot.html#faq ___ 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
Michael Hudson wrote: > >> +* Remove support for old systems, including: OS2, BeOS, RISCOS, (SGI) > >> Irix, Tru64 > > > > what's old with tru64 ? it's not that uncommon in places where Python > > has a strong presence, you can still buy AXP hardware throughout 2006, > > and HP says they'll keep developing and supporting the software platform > > at least through 2011. > > And we still have someone actively interested in maintaining the OS2 > port, it seems. fwict, OS/2 will be officially supported throughout this year. not sure about Irix; the roadmaps don't seem to be available to non-paying 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] r43214 - peps/trunk/pep-3000.txt
Michael Hudson wrote: > "Fredrik Lundh" <[EMAIL PROTECTED]> writes: > >> neal.norwitz wrote: >> >>> +Outstanding Issues >>> +== >>> + >>> +* Require C99, so we can use // comments, named initializers, declare >>> variables >>> + without introducing a new scope, among other benefits. >> gcc only, in other words ? > > Heh, I was going to make this point as well: it's not clear that MSVC > will ever support C99. It supports some of the features listed here, > of course, but probably won't support everything. Given the list of features Neal mentioned, I don't think these really warrant going for full C99. >>> +* Remove support for old systems, including: OS2, BeOS, RISCOS, (SGI) >>> Irix, Tru64 >> what's old with tru64 ? it's not that uncommon in places where Python >> has a strong presence, you can still buy AXP hardware throughout 2006, >> and HP says they'll keep developing and supporting the software platform >> at least through 2011. > > And we still have someone actively interested in maintaining the OS2 > port, it seems. Dito for BeOS, now under the name Zeta OS. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 22 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] Py3k: Except clause syntax
* Greg Ewing <[EMAIL PROTECTED]> [2006-03-21 13:20:53 +1200]: > Gareth McCaughan wrote: > > > but wouldn't if be nice if you could say > > > > def f((x0,y0) as p0, (x1,y1) as p1): > > I'm not sure that it would. Currently you can look at > a function header and get a picture of its calling > signature, but this would clutter it up with > implementation details of the function that aren't > relevant to the caller. For maximal utility, this would affect the calling signature of the function, too: it would now have keyword arguments named p0 and p1. -- mithrandi, i Ainil en-Balandor, a faer Ambar signature.asc Description: Digital 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/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/111 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: thomas.heller 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 g4 osx.4 trunk
The Buildbot has detected a new failure of g4 osx.4 trunk. Full details are available at: http://www.python.org/dev/buildbot/all/g4%20osx.4%20trunk/builds/105 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: thomas.heller 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 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/113 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: thomas.heller 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 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/108 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: thomas.heller 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 amd64 gentoo trunk
The Buildbot has detected a new failure of amd64 gentoo trunk. Full details are available at: http://www.python.org/dev/buildbot/all/amd64%20gentoo%20trunk/builds/115 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: barry.warsaw 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] Building Python for AMD64 (Windows)
I'm trying out to build Python for 64-bit Windows, running the tools on WinXP SP2 (32-bit). I have installed: - MSVC .NET 2003 - Platform SDK Feb 2003 - vsextcomp 0.6 Then I fire up MSVC, select the ReleaseAMD64 configuration, and try to build the pythoncore project. After lots of compiler warnings, the build fails with this message: cl.exe -c -D_WIN32 -DUSE_DL_EXPORT -D_WINDOWS -DWIN32 -D_WINDLL -MD -MD /USECL:MS_OPTERON getbuildinfo2.c -DSUBWCREV -Fogetbuildinfo.o -I..\Include -I..\PC Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 Copyright (C) Microsoft Corporation 1984-2002. All rights reserved. getbuildinfo2.c Linking... LINK : warning LNK4044: unrecognized option '/USELINK:MS_SDK'; ignored getbuildinfo.o : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'AMD64' Build log was saved at "file://c:\svn\trunk\PCbuild\amd64-temp-release\pythoncore\BuildLog.htm" pythoncore - 1 error(s), 229 warning(s) Is there something wrong on my side? Thanks, 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
Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt
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. 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] Building Python for AMD64 (Windows)
Thomas Heller wrote: > Then I fire up MSVC, select the ReleaseAMD64 configuration, and try to build > the > pythoncore project. > After lots of compiler warnings, the build fails with this message: > > cl.exe -c -D_WIN32 -DUSE_DL_EXPORT -D_WINDOWS -DWIN32 -D_WINDLL -MD -MD > /USECL:MS_OPTERON getbuildinfo2.c -DSUBWCREV -Fogetbuildinfo.o -I..\Include > -I..\PC > Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 > Copyright (C) Microsoft Corporation 1984-2002. All rights reserved. > getbuildinfo2.c > Linking... > LINK : warning LNK4044: unrecognized option '/USELINK:MS_SDK'; ignored > getbuildinfo.o : fatal error LNK1112: module machine type 'X86' conflicts > with target machine type 'AMD64' > > Build log was saved at > "file://c:\svn\trunk\PCbuild\amd64-temp-release\pythoncore\BuildLog.htm" > pythoncore - 1 error(s), 229 warning(s) > > Is there something wrong on my side? For some reason, VS.NET hasn't picked up the PATH modifications, so that it doesn't invoke the linker wrapper (which would have invoked the right compiler and linker). This sometimes happens, and I don't know why. As the first measure, open Tools/External compiler configuration, and see whether this reports changes to the path. If it does, throw all object files away, and recompile. Otherwise, please try editing the executable path manually: Tools/Options/Projects/VC++ Directories/Executable Files should start with c:\program files\vsextcompiler. Please let me know whether that works. 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
Would it be possible to redirect these buildbot messages to the python-checkins or a separate python-buildbot list ? Original Message Subject: [Python-Dev] buildbot warnings in amd64 gentoo trunk Date: Wed, 22 Mar 2006 15:18:20 + From: [EMAIL PROTECTED] Reply-To: python-dev@python.org To: python-dev@python.org The Buildbot has detected a new failure of amd64 gentoo trunk. Full details are available at: http://www.python.org/dev/buildbot/all/amd64%20gentoo%20trunk/builds/115 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: barry.warsaw 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/mal%40egenix.com -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 22 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] Building Python for AMD64 (Windows)
Martin v. Löwis wrote: > Thomas Heller wrote: >> Then I fire up MSVC, select the ReleaseAMD64 configuration, and try to >> build the >> pythoncore project. >> After lots of compiler warnings, the build fails with this message: >> ... > > For some reason, VS.NET hasn't picked up the PATH modifications, so that > it doesn't invoke the linker wrapper (which would have invoked the right > compiler and linker). This sometimes happens, and I don't know why. > > As the first measure, open Tools/External compiler configuration, and > see whether this reports changes to the path. If it does, throw all > object files away, and recompile. > > Otherwise, please try editing the executable path manually: > > Tools/Options/Projects/VC++ Directories/Executable Files > > should start with c:\program files\vsextcompiler. > > Please let me know whether that works. Yes, that worked. vsextcomp complained that the PATH was not correct, but it did then repair it itself. Ok, so now I'm able to make itanium builds (which I don't want because I don't have such amachine). The Feb 2003 Platform SDK apparently doesn't have an AMD64 compiler. In the meantime, I installed a fresh copy of MSVC on a second machine (Athlon64, running Windows XP 64bit), plus the Platform SDK for Win Server 2003 SP1 - April 2005 Edition. Same problems with vsextcomp, but vsextcomp repairs the path itself again. But here, starting the build it complains: CL.EXE Wrapper for VSExtCompiler Plugin Error 2 while trying to open SDK path key from registry ... Error: Could not determine installation directory of Microsoft SDK. Guess I'll install the 2003 SP1 SDK on the first machine and try it there. 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
Re: [Python-Dev] PY_SSIZE_T_CLEAN
Martin v. Löwis wrote: > Thomas Heller wrote: >> Then, from only reading the PEP without looking up the sources, >> it is not clear to me what the PY_SIZE_T_CLEAN definition does. > > The description says > > The conversion codes 's#' and 't#' will output Py_ssize_t > if the macro PY_SSIZE_T_CLEAN is defined before Python.h > is included, and continue to output int if that macro > isn't defined. > > which (IMO, of course), specifies precisely what PY_SSIZE_T_CLEAN > does. What information do you find lacking here? Nothing lacking. It is fine - I didn't read it carefully enough. Thanks, 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
Re: [Python-Dev] Building Python for AMD64 (Windows)
Thomas Heller wrote: > Martin v. Löwis wrote: >> Thomas Heller wrote: >>> Then I fire up MSVC, select the ReleaseAMD64 configuration, and try to >>> build the >>> pythoncore project. >>> After lots of compiler warnings, the build fails with this message: >>> > ... >> For some reason, VS.NET hasn't picked up the PATH modifications, so that >> it doesn't invoke the linker wrapper (which would have invoked the right >> compiler and linker). This sometimes happens, and I don't know why. >> >> As the first measure, open Tools/External compiler configuration, and >> see whether this reports changes to the path. If it does, throw all >> object files away, and recompile. >> >> Otherwise, please try editing the executable path manually: >> >> Tools/Options/Projects/VC++ Directories/Executable Files >> >> should start with c:\program files\vsextcompiler. >> >> Please let me know whether that works. > > Yes, that worked. vsextcomp complained that the PATH was not correct, but it > did then repair it itself. > > Ok, so now I'm able to make itanium builds (which I don't want because I > don't have > such amachine). The Feb 2003 Platform SDK apparently doesn't have an AMD64 > compiler. > > In the meantime, I installed a fresh copy of MSVC on a second machine > (Athlon64, running > Windows XP 64bit), plus the Platform SDK for Win Server 2003 SP1 - April 2005 > Edition. > > Same problems with vsextcomp, but vsextcomp repairs the path itself again. > But here, starting the build it complains: > CL.EXE Wrapper for VSExtCompiler Plugin > Error 2 while trying to open SDK path key from registry ... > Error: Could not determine installation directory of Microsoft SDK. > > Guess I'll install the 2003 SP1 SDK on the first machine and try it there. Ok, the Win32 Server 2003 SP1 April 2005 SDK is installed on the first machine, the build now fails with this: -- Build started: Project: pythoncore, Configuration: ReleaseAMD64 Win32 -- Compiling resources... generate buildinfo "C:\Programme\TortoiseSVN\bin\subwcrev.exe" .. ..\Modules\getbuildinfo.c getbuildinfo2.c SubWCRev: 'c:\svn\trunk' Last committed at revision 43226 Updated to revision 43226 Local modifications found cl.exe -c -D_WIN32 -DUSE_DL_EXPORT -D_WINDOWS -DWIN32 -D_WINDLL -MD -MD /USECL:MS_OPTERON getbuildinfo2.c -DSUBWCREV -Fogetbuildinfo.o -I..\Include -I..\PC getbuildinfo2.c -- CL.EXE Wrapper for VSExtCompiler Plugin -- 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...) gzio.obj : error LNK2001: unresolved external symbol __security_check_cookie inftrees.obj : error LNK2001: unresolved external symbol __security_check_cookie trees.obj : error LNK2001: unresolved external symbol __security_check_cookie _codecs_cn.obj : error LNK2001: unresolved external symbol __security_check_cookie ./python25.dll : fatal error LNK1120: 2 unresolved externals -- LINK.EXE Wrapper for VSExtCompiler Plugin -- Build log was saved at "file://c:\svn\trunk\PCbuild\amd64-temp-release\pythoncore\BuildLog.htm" pythoncore - 107 error(s), 0 warning(s) -- Done -- Build: 2 succeeded, 1 failed, 0 skipped Is there a library missing? BTW: When this eventually builds, will this run on an Athlon64, or does it need an Opteron processor? 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
Re: [Python-Dev] Building Python for AMD64 (Windows)
[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? Trent -- Trent Mick [EMAIL PROTECTED] diff Must link with bufferoverflowU.lib for Win64 builds of some binaries with the latest Platform SDK to avoid errors a la (c.f. http://support.microsoft.com/?id=894573): 'unresolved external symbol __security_cookie' errors. diff -ur python/PCbuild.original/_bsddb.vcproj python/PCbuild/_bsddb.vcproj --- python/PCbuild.original/_bsddb.vcproj Thu Aug 12 07:07:49 2004 +++ python/PCbuild/_bsddb.vcprojThu Jun 02 16:41:43 2005 @@ -179,7 +179,7 @@ ___ 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)
Thomas Heller wrote: > Ok, so now I'm able to make itanium builds (which I don't want because I > don't have such amachine). The Feb 2003 Platform SDK apparently doesn't have > an > AMD64 compiler. Right. The Itanium compiler was included in the November 2004 (or so) SDK (which called itself still Feb 2003); this was available only to MSDN subscribers. > In the meantime, I installed a fresh copy of MSVC on a second machine > (Athlon64, running > Windows XP 64bit), plus the Platform SDK for Win Server 2003 SP1 - April > 2005 Edition. That one does have the AMD64 compiler. > Same problems with vsextcomp, but vsextcomp repairs the path itself again. > But here, starting the build it complains: > CL.EXE Wrapper for VSExtCompiler Plugin > Error 2 while trying to open SDK path key from registry ... > Error: Could not determine installation directory of Microsoft SDK. > > Guess I'll install the 2003 SP1 SDK on the first machine and try it there. No. I thought I had released that version of vsextcomp... MS changed the registry keys to locate the SDK, and vsextcomp had to be updated for that. Will check tomorrow. 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
M.-A. Lemburg wrote: > Would it be possible to redirect these buildbot messages to the > python-checkins or a separate python-buildbot list ? Sure. They are sent to python-dev, because I think Tim Peters wanted them here. 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] Building Python for AMD64 (Windows)
Thomas Heller wrote: > Is there a library missing? Either that (although I forgot the library name - google knows it), or a command line option missing: there is an option to suppress usage of these security check symbols. It appears that VS 2005 has them disabled by default, whereas the SDK compilers have enabled them by default. I think Python should not link with these libraries, but disable the feature instead. > BTW: When this eventually builds, will this run on an Athlon64, or > does it need an Opteron processor? It should run on any AMD64 processor, including Intel processors with EM64T. 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
Martin v. Löwis wrote: > M.-A. Lemburg wrote: >> Would it be possible to redirect these buildbot messages to the >> python-checkins or a separate python-buildbot list ? > > Sure. They are sent to python-dev, because I think Tim Peters > wanted them here. 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. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 22 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] Py3k: Except clause syntax
Tristan Seligmann wrote: > Greg Ewing <[EMAIL PROTECTED]> [2006-03-21 13:20:53 +1200]: > > Gareth McCaughan wrote: > > > > > >def f((x0,y0) as p0, (x1,y1) as p1): > For maximal utility, this would affect the calling signature of the > function, too: it would now have keyword arguments named p0 and p1. I still think it hurts readability of the header too much to be worth the benefit. To me it would seem much clearer all round to write def f(p0, p1): x0, y0 = p0 x1, y1 = p1 -- Greg Ewing, Computer Science Dept, +--+ University of Canterbury, | Carpe post meridiam! | Christchurch, New Zealand | (I'm not a morning person.) | [EMAIL PROTECTED] +--+ ___ 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/116 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: neal.norwitz 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]
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. You still can opt-out, by filtering messages that originate from [EMAIL PROTECTED] 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] [Fwd: buildbot warnings in amd64 gentoo trunk]
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. 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 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/111 Buildbot URL: http://www.python.org/dev/buildbot/all/ Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: neal.norwitz 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
