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 t
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 examp
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
__
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:
> > >
>
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
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
listenin
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
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 p
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
>> >> bu
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.
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
> 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 g
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 workin
>> 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/
>> htt
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.
Tha
-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 R
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/optio
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
> w
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
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 were
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://
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
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/
Th
23 matches
Mail list logo
