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
Bla
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 fo
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 a
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
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
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 maili
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 compi
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
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 s
[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: unresol
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
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_CLEA
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 modificat
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@p
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 ge
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.
Re
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 warni
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.war
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
Bla
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
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
Bu
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
* 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
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 benefi
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
"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 ?
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, Be
27 matches
Mail list logo
