[Python-Dev] fixing broken build

[Neal Norwitz]

Christian,

Please fix the build on the various buildbots that are failing or
revert your changes for unicode literals.  The build failures started
to occur at r61953.  There were several more (~5) follow up checkins.

You can find all the failures here:  http://www.python.org/dev/buildbot/all/

There seem to be at least two variations for how setup.py is failing.
See below.

n
--

Traceback (most recent call last):
  File "./setup.py", line 6, in 
import sys, os, imp, re, optparse
  File "/opt/users/buildbot/slave/trunk.loewis-sun/build/Lib/optparse.py",
line 71, in 
import textwrap
  File "/opt/users/buildbot/slave/trunk.loewis-sun/build/Lib/textwrap.py",
line 32, in 
class TextWrapper:
  File "/opt/users/buildbot/slave/trunk.loewis-sun/build/Lib/textwrap.py",
line 84, in TextWrapper
r'(\s+|'  # any whitespace
  File "/opt/users/buildbot/slave/trunk.loewis-sun/build/Lib/re.py",
line 188, in compile
return _compile(pattern, flags)
  File "/opt/users/buildbot/slave/trunk.loewis-sun/build/Lib/re.py",
line 239, in _compile
raise TypeError, "first argument must be string or compiled pattern"
TypeError: first argument must be string or compiled pattern

Traceback (most recent call last):
  File "./setup.py", line 13, in 
from distutils.core import Extension, setup
  File 
"/home/buildbot/slave/py-build/trunk.norwitz-amd64/build/Lib/distutils/core.py",
line 21, in 
from distutils.dist import Distribution
  File 
"/home/buildbot/slave/py-build/trunk.norwitz-amd64/build/Lib/distutils/dist.py",
line 21, in 
from distutils.fancy_getopt import FancyGetopt, translate_longopt
  File 
"/home/buildbot/slave/py-build/trunk.norwitz-amd64/build/Lib/distutils/fancy_getopt.py",
line 32, in 
longopt_xlate = string.maketrans('-', '_')
  File "/home/buildbot/slave/py-build/trunk.norwitz-amd64/build/Lib/string.py",
line 76, in maketrans
return ''.join(L)
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position
0: ordinal not in range(128)
___
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] Decimal(unicode)

[Greg Ewing]

Nick Coghlan wrote:
> I believe the list of incompatibilities and kludges and the subsequent 
> comments in the following file give the gist of the problems:
> http://svn.python.org/projects/sandbox/trunk/decimal-c/_decimal.c

It sounds like some aspects of the API weren't thought
through very well when the Python version was designed.

The question now is whether to fix the API design, or
leave it to become entrenched and lose all hope of
ever having a fully C-coded implementation.

-- 
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

Re: [Python-Dev] fixing broken build

[Christian Heimes]

Neal Norwitz schrieb:
> Christian,
> 
> Please fix the build on the various buildbots that are failing or
> revert your changes for unicode literals.  The build failures started
> to occur at r61953.  There were several more (~5) follow up checkins.
> 
> You can find all the failures here:  http://www.python.org/dev/buildbot/all/
> 
> There seem to be at least two variations for how setup.py is failing.
> See below.

I've already fixed the problem in r61956. I didn't noticed the issue
with a non initialized var until I compiled Python without pydebug. In
order to fix the problem on the build bots one has to remove all pyc and
pyo files.

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] Decimal(unicode)

[Georg Brandl]

Greg Ewing schrieb:
> Nick Coghlan wrote:
>> I believe the list of incompatibilities and kludges and the subsequent 
>> comments in the following file give the gist of the problems:
>> http://svn.python.org/projects/sandbox/trunk/decimal-c/_decimal.c
> 
> It sounds like some aspects of the API weren't thought
> through very well when the Python version was designed.
> 
> The question now is whether to fix the API design, or
> leave it to become entrenched and lose all hope of
> ever having a fully C-coded implementation.

As Nick said, a drop-in replacement in C isn't feasible

But probably users of decimal won't really care if they have to slightly
adapt their code if they get the speed increase instead.

We had a SOC student working on decimal-c in the past, so it shouldn't be
totally dead. What about this year's SOC?

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
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] fixing broken build

[M.-A. Lemburg]

On 2008-03-27 09:20, Christian Heimes wrote:
> Neal Norwitz schrieb:
>> Christian,
>>
>> Please fix the build on the various buildbots that are failing or
>> revert your changes for unicode literals.  The build failures started
>> to occur at r61953.  There were several more (~5) follow up checkins.
>>
>> You can find all the failures here:  http://www.python.org/dev/buildbot/all/
>>
>> There seem to be at least two variations for how setup.py is failing.
>> See below.
> 
> I've already fixed the problem in r61956. I didn't noticed the issue
> with a non initialized var until I compiled Python without pydebug. In
> order to fix the problem on the build bots one has to remove all pyc and
> pyo files.

I'm not sure why that's necessary, but whenever you change something
in the compiler, please remember to update the PYC magic.

I'd also suggest that you run a non-debug build of Python to test
any checkins before committing them. The debug builds change various
ways the code is built.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Mar 27 2008)
 >>> 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,MacOSX for free ! 


eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
___
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] fixing broken build

[Christian Heimes]

M.-A. Lemburg schrieb:
> I'm not sure why that's necessary, but whenever you change something
> in the compiler, please remember to update the PYC magic.
> 
> I'd also suggest that you run a non-debug build of Python to test
> any checkins before committing them. The debug builds change various
> ways the code is built.

Changing the pyc magic isn't required here. Some files were compiled to
bytecode with the wrong flags because I didn't initialize the flags
correctly. I (ab)used a temporary change of the magic to force a
recompilation of bytecode. All build bots are fine again.

I usually don't test the new code with a non-debug build unless a
release is immanent. A full test run already takes a considerable amount
of time (>10 minutes) and debug builds usually catch more errors than
plain builds. I've to draw the line somewhere ...

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

[Python-Dev] UCS-4 build on build bots

[Christian Heimes]

Can we have at least one build bot that compiles Python with UCS-4
unicode instead of UCS-2?

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] UCS-4 build on build bots

[Jeroen Ruigrok van der Werven]

-On [20080327 13:09], Christian Heimes ([EMAIL PROTECTED]) wrote:
>Can we have at least one build bot that compiles Python with UCS-4
>unicode instead of UCS-2?

Feel free to add another configuration for my machine. Only caveat is the
curses test, which I am still tracking.

-- 
Jeroen Ruigrok van der Werven  / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
To fight and conquer in one hundred battles is not the highest skill. To
subdue the enemy with no fight at all, that's the highest skill...
___
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] Decimal(unicode)

[Facundo Batista]

2008/3/26, Nick Coghlan <[EMAIL PROTECTED]>:

>  Basically, while it makes a lot of sense to move the *arithmetic* to C
>  (as Mark mentioned in his other post), there's a lot of ancillary stuff
>  related to flags and exceptions and context handling that is much easier
>  to handle in Python.

That's why we think that the most probably future move here is:

1. Code a small core in C.

2. Let the rest of Decimal in Py.

"small core" and "rest of Decimal" are moving targets we (as
python-dev) could decide that __add__ is really worthy to do it in C,
but not quantize(), for example.

Regards,

-- 
.Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
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-3000] the release gods are angry at python

[skip]

>> The next releases of 2.6/3.0 are planned for April 2, just over a
>> week from now.  There is much work that needs to be done.  The
>> buildbots are in a pretty sad state and the gods are seeing too much
>> red.
>> 
>> http://www.python.org/dev/buildbot/stable/
>> http://www.python.org/dev/buildbot/all/

Is there some reason the "g4 osx.4 trunk" buildbot isn't running?  When I
checked it this morning it was idle with two pending.  I forced a run.  I
checked later today and it showed five pending.  Now it shows 10 pending.
It looks like its last run was about 18 hours ago.  You would think by now
it would have been able to make another run.  It pings fine.

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

Re: [Python-Dev] Decimal(unicode)

[Mark Dickinson]

On Thu, Mar 27, 2008 at 4:46 AM, Georg Brandl <[EMAIL PROTECTED]> wrote:

> As Nick said, a drop-in replacement in C isn't feasible
>
> But probably users of decimal won't really care if they have to slightly
> adapt their code if they get the speed increase instead.
>
> We had a SOC student working on decimal-c in the past, so it shouldn't be
> totally dead. What about this year's SOC?
>

I worry that rewriting Decimal in C in its entirety would make it
significantly harder to maintain.  The IBM Decimal Specification
hasn't stabilised yet:  there's another update to it expected some
time after IEEE 754r is finally approved, so there are probably
still significant changes to be made to Decimal in the future.

I know that I would have contributed a lot less to Decimal had
it been written in C, simply because it would have taken me
much more time to understand and modify the code.

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-3000] the release gods are angry at python

[Bill Janssen]

> There
> have been other tests that have also been flaky like  test_asynchat,
> test_smtplib, test_ssl, test_urllib2net, test_urllibnet,
> test_xmlrpc_net and some of the tests that use  networking.

Some of the *other* tests that use networking, I think you mean.
Sounds like networking tests in general are flaky.

> - 
> http://www.python.org/dev/buildbot/all/S-390%20Debian%20trunk/builds/255/step-test/0

Unfortunately, this log has no information about why the test is
failing, and I do not have a Debian-unstable machine to try it on
(much less a six-processor IBM S/390 mainframe running Debian-unstable
-- cool!).  I'm unsure about how to make progress here.  It's
interesting to see that most of the stable buildbots running Debian
are doing so on big-endian (PPC, Sparc) hardware.

I also can't tell which branch of Python is being tested, from this
logfile.  That would be nice to add.  Is this 2.6 (known problems with
SSL) or 3.0 (no known problems with SSL)?  Is this information in the
logfile somewhere and I'm not seeing it?

Bill
___
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-3000] the release gods are angry at python

[Michael Foord]

Bill Janssen wrote:
>> There
>> have been other tests that have also been flaky like  test_asynchat,
>> test_smtplib, test_ssl, test_urllib2net, test_urllibnet,
>> test_xmlrpc_net and some of the tests that use  networking.
>> 
>
> Some of the *other* tests that use networking, I think you mean.
> Sounds like networking tests in general are flaky.
>   

This patch was put together at PyCon (but has not been applied): 
http://bugs.python.org/issue2429

It moves some of the urllib2net tests to urllib2localnet - they use a 
local server instead of going out to external servers and should be more 
reliable.

Michael

>   
>> - 
>> http://www.python.org/dev/buildbot/all/S-390%20Debian%20trunk/builds/255/step-test/0
>> 
>
> Unfortunately, this log has no information about why the test is
> failing, and I do not have a Debian-unstable machine to try it on
> (much less a six-processor IBM S/390 mainframe running Debian-unstable
> -- cool!).  I'm unsure about how to make progress here.  It's
> interesting to see that most of the stable buildbots running Debian
> are doing so on big-endian (PPC, Sparc) hardware.
>
> I also can't tell which branch of Python is being tested, from this
> logfile.  That would be nice to add.  Is this 2.6 (known problems with
> SSL) or 3.0 (no known problems with SSL)?  Is this information in the
> logfile somewhere and I'm not seeing it?
>
> Bill
> ___
> 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/fuzzyman%40voidspace.org.uk
>   

___
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-3000] the release gods are angry at python

[Neal Norwitz]

On Wed, Mar 26, 2008 at 5:52 PM,  <[EMAIL PROTECTED]> wrote:
> >> The next releases of 2.6/3.0 are planned for April 2, just over a
> >> week from now.  There is much work that needs to be done.  The
> >> buildbots are in a pretty sad state and the gods are seeing too much
> >> red.
> >>
> >> http://www.python.org/dev/buildbot/stable/
> >> http://www.python.org/dev/buildbot/all/
>
>  Is there some reason the "g4 osx.4 trunk" buildbot isn't running?  When I
>  checked it this morning it was idle with two pending.  I forced a run.  I
>  checked later today and it showed five pending.  Now it shows 10 pending.
>  It looks like its last run was about 18 hours ago.  You would think by now
>  it would have been able to make another run.  It pings fine.

I logged in to the machine an the buildbot is running.  I think what
happens is that sometimes the master loses track of the slaves.  The
fix requires restarting the master, but I didn't want to do that last
night while there were still builds going on.  I'll try to find a
quiet time tonight and restart the master.  I expect that will fix the
problem.

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-3000] the release gods are angry at python

[Jean-Paul Calderone]

On Thu, 27 Mar 2008 11:43:25 -0700, Neal Norwitz <[EMAIL PROTECTED]> wrote:
>On Wed, Mar 26, 2008 at 5:52 PM,  <[EMAIL PROTECTED]> wrote:
>> >> The next releases of 2.6/3.0 are planned for April 2, just over a
>> >> week from now.  There is much work that needs to be done.  The
>> >> buildbots are in a pretty sad state and the gods are seeing too much
>> >> red.
>> >>
>> >> http://www.python.org/dev/buildbot/stable/
>> >> http://www.python.org/dev/buildbot/all/
>>
>>  Is there some reason the "g4 osx.4 trunk" buildbot isn't running?  When I
>>  checked it this morning it was idle with two pending.  I forced a run.  I
>>  checked later today and it showed five pending.  Now it shows 10 pending.
>>  It looks like its last run was about 18 hours ago.  You would think by now
>>  it would have been able to make another run.  It pings fine.
>
>I logged in to the machine an the buildbot is running.  I think what
>happens is that sometimes the master loses track of the slaves.  The
>fix requires restarting the master, but I didn't want to do that last
>night while there were still builds going on.  I'll try to find a
>quiet time tonight and restart the master.  I expect that will fix the
>problem.
>

There's a bug in some configurations (I have never managed to track down
the details) where the ping action actually prevents any further builds
from happening on that slave until the master is restarted.  Not sure if
this is related to the problem you're seeing here or not.

Jean-Paul
___
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-3000] the release gods are angry at python

[David Bolen]

Jean-Paul Calderone <[EMAIL PROTECTED]> writes:

> There's a bug in some configurations (I have never managed to track down
> the details) where the ping action actually prevents any further builds
> from happening on that slave until the master is restarted.  Not sure if
> this is related to the problem you're seeing here or not.

Over time, I've seen this occasionally in the status for my buildbots
(idle, but builds shown as pending, and yes often the last action was
a ping).  At least in the cases I've observed into so far, restarting
the buildbot has typically cleaned it up and let the builds proceed.

-- David

___
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] Backport of bytearray type and io module

[Benjamin Peterson]

On Wed, Mar 26, 2008 at 11:58 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:

> Yay indeed! Of course the new I/O module will undergo changes (Ping is
> working on it still I believe). Try to keep an eye on it so the
> improvements can be backported.

So improvements to backported features will be merged into 2.6?

>
>
> On Wed, Mar 26, 2008 at 6:00 AM, Facundo Batista
> <[EMAIL PROTECTED]> wrote:
> > 2008/3/26, Christian Heimes <[EMAIL PROTECTED]>:
> >
> >
> > > Correct!
> >  >
> >  >  The bytearray type and the new IO system are now backported to
> Python 2.6.
> >
> >  Thank you very much for this effort!
> >
> >  Regards,
> >
> >
> >
> >  --
> >  .Facundo
> >
> >  Blog: http://www.taniquetil.com.ar/plog/
> >  PyAr: http://www.python.org/ar/
> >
>
>
>
> --
> --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/musiccomposition%40gmail.com
>



-- 
Cheers,
Benjamin Peterson
___
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-3000] the release gods are angry at python

[Ralf Schmitt]

On Wed, Mar 26, 2008 at 7:21 AM, Neal Norwitz <[EMAIL PROTECTED]> wrote:

>  * test_xmlrpc transient socket errors
>-
> http://www.python.org/dev/buildbot/stable/g4%20osx.4%20trunk/builds/3101/step-test/0
>
>

These are caused by the accept call returning a nonblocking socket, when the
listening socket itself is nonblocking (which it is). see
http://bugs.python.org/issue1503 for more details.
___
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] Commit access request

[Benjamin Peterson]

On Tue, Mar 25, 2008 at 3:27 PM, Benjamin Peterson <
[EMAIL PROTECTED]> wrote:

>
>
> On Tue, Mar 25, 2008 at 12:40 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
> > Georg Brandl schrieb:
> > > Benjamin Peterson schrieb:
> > >> Hi Python devs,
> > >> I have been contributing to since December. (See me first issue on
> > the
> > >> tracker, #1828; it was a major learning experience.) :P In that time,
> > I
> > >> have contributed many patches and actively participated on this list.
> > >> This will enable me to help triage bugs on the tracker, something
> > I've
> > >> been wanting to help with.
> > >
> > > I'm +1 to Benjamin getting commit privileges, letting commits sign off
> > > by a senior developer.
> >
> > Since there are no objections, I've now added Benjamin's key, under that
> > condition.
>
> Thanks!
>
> >
> >
> > Welcome on board, Benjamin! :)
>
> One more question: Do I get a @python.org email alias?

> Glad to help!
>
> >
> >
> > Georg
> >
> >
> > --
> > Thus spake the Lord: Thou shalt indent with four spaces. No more, no
> > less.
> > Four shall be the number of spaces thou shalt indent, and the number of
> > thy
> > indenting shall be four. Eight shalt thou not indent, nor either indent
> > thou
> > two, excepting that thou then proceed to four. Tabs are right out.
> >
> > ___
> > 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/musiccomposition%40gmail.com
> >
>
>
>
> --
> Cheers,
> Benjamin Peterson




-- 
Cheers,
Benjamin Peterson
___
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] Commit access request

[Brett Cannon]

On Thu, Mar 27, 2008 at 2:25 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Tue, Mar 25, 2008 at 3:27 PM, Benjamin Peterson
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > On Tue, Mar 25, 2008 at 12:40 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> >
> > > Georg Brandl schrieb:
> > >
> > > > Benjamin Peterson schrieb:
> > > >> Hi Python devs,
> > > >> I have been contributing to since December. (See me first issue on
> the
> > > >> tracker, #1828; it was a major learning experience.) :P In that time,
> I
> > > >> have contributed many patches and actively participated on this list.
> > > >> This will enable me to help triage bugs on the tracker, something
> I've
> > > >> been wanting to help with.
> > > >
> > > > I'm +1 to Benjamin getting commit privileges, letting commits sign off
> > > > by a senior developer.
> > >
> > > Since there are no objections, I've now added Benjamin's key, under that
> > > condition.
> >
> > Thanks!
> >
> > >
> > >
> > > Welcome on board, Benjamin! :)
> >
> One more question: Do I get a @python.org email alias?

Not by default. That has typically been given to people who have
contributed to the web site.

-Brett
___
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] Decimal(unicode)

[Greg Ewing]

Georg Brandl wrote:

> As Nick said, a drop-in replacement in C isn't feasible

Yes, but that appears to be so only because of some
unfortunate features of the Python version's API.

Seems to me it would be better to undergo a little
pain now and get a well-designed C-friendly API.

-- 
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

Re: [Python-Dev] Decimal(unicode)

[Mark Dickinson]

On Thu, Mar 27, 2008 at 4:46 AM, Georg Brandl <[EMAIL PROTECTED]> wrote:

>
> As Nick said, a drop-in replacement in C isn't feasible
>
> But probably users of decimal won't really care if they have to slightly
> adapt their code if they get the speed increase instead.
>

Could you give me an example of the sort of adaptations that might be
necessary, or the API changes that would be necessary to make a
drop-in replacement possible?

Are you just talking about things like removing the context argument
from __add__ and friends, or is it more serious than this?

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-3000] the release gods are angry at python

[Neal Norwitz]

On Thu, Mar 27, 2008 at 11:31 AM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > There
>  > have been other tests that have also been flaky like  test_asynchat,
>  > test_smtplib, test_ssl, test_urllib2net, test_urllibnet,
>  > test_xmlrpc_net and some of the tests that use  networking.
>
>  Some of the *other* tests that use networking, I think you mean.

Yes, primarily networking tests.  Also things like signals and threading.

>  Sounds like networking tests in general are flaky.

Anything that connects to a remote host is definitely flaky.  Most of
the tests that connect to localhost are flaky for one reason or
another.  One reason used to be port allocation.  That is mostly fixed
now.

The big reason that most tests fail now is EAGAIN or some other error,
typically on non-blocking sockets.  Switching to blocking sockets
isn't really a great option since the tests are much more likely to
hang.

>  > - 
> http://www.python.org/dev/buildbot/all/S-390%20Debian%20trunk/builds/255/step-test/0
>
>  Unfortunately, this log has no information about why the test is
>  failing, and I do not have a Debian-unstable machine to try it on
>  (much less a six-processor IBM S/390 mainframe running Debian-unstable
>  -- cool!).  I'm unsure about how to make progress here.  It's
>  interesting to see that most of the stable buildbots running Debian
>  are doing so on big-endian (PPC, Sparc) hardware.
>
>  I also can't tell which branch of Python is being tested, from this
>  logfile.  That would be nice to add.  Is this 2.6 (known problems with
>  SSL) or 3.0 (no known problems with SSL)?  Is this information in the
>  logfile somewhere and I'm not seeing it?

The information happens to be encoded in the URL.  The URL above is for trunk.
You can see more info here:  http://www.python.org/dev/buildbot/all/
That is the landing page for all the info you could want.  Well,
mostly.  The logs often don't really have enough info to debug the
problem.  In that case, it would be better to add more debugging to
the tests.

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