On Tue, Apr 19, 2011 at 3:06 PM, Stefan Behnel wrote:
> I think this social problem of the PEP can only be solved if the CPython
> project stops doing the major share of the stdlib maintenance, thus freeing
> its own developer capacities to focus on CPython related improvements and
> optimisations
Nick Coghlan, 19.04.2011 10:57:
On Tue, Apr 19, 2011 at 3:06 PM, Stefan Behnel wrote:
I think this social problem of the PEP can only be solved if the CPython
project stops doing the major share of the stdlib maintenance, thus freeing
its own developer capacities to focus on CPython related impr
On Tue, 19 Apr 2011 09:47:21 +0200
giampaolo.rodola wrote:
> http://hg.python.org/cpython/rev/8c49f7fbba1d
> changeset: 69437:8c49f7fbba1d
> user:Giampaolo Rodola'
> date:Tue Apr 19 09:47:16 2011 +0200
> summary:
> os.sendfile(): on Linux if offset parameter is passed as NULL
On Tue, Apr 19, 2011 at 1:06 AM, Stefan Behnel wrote:
[snip]
> This PEP has received a lengthy discussion by now, so here's why I think
> it's being fought so heavily by several CPython core developers,
> specifically those who have traditionally carried a large part of the
> optimisation load in
On Tue, Apr 19, 2011 at 10:57 AM, Nick Coghlan wrote:
> On Tue, Apr 19, 2011 at 3:06 PM, Stefan Behnel wrote:
>> I think this social problem of the PEP can only be solved if the CPython
>> project stops doing the major share of the stdlib maintenance, thus freeing
>> its own developer capacities
On Tue, Apr 19, 2011 at 8:17 AM, Maciej Fijalkowski wrote:
> On Tue, Apr 19, 2011 at 10:57 AM, Nick Coghlan wrote:
>> On Tue, Apr 19, 2011 at 3:06 PM, Stefan Behnel wrote:
>>> I think this social problem of the PEP can only be solved if the CPython
>>> project stops doing the major share of the
On Mon, Apr 18, 2011 at 3:53 PM, Barry Warsaw wrote:
> With Martin getting ready to release 2.5.6, I think it's time to prepare a
> 2.6.7 source-only security release.
>
> I'll work my way through the NEWS file and recent commits, but if there is
> anything that you know is missing from the 2.6 br
On Tue, Apr 19, 2011 at 12:01 PM, Stefan Behnel wrote:
> Nick Coghlan, 19.04.2011 10:57:
>>
>> On Tue, Apr 19, 2011 at 3:06 PM, Stefan Behnel wrote:
>>>
>>> I think this social problem of the PEP can only be solved if the CPython
>>> project stops doing the major share of the stdlib maintenance, t
>
> Once this move is made/accepted, I would expect the other
> implementation to rapidly move away from their custom implementations
> of the stdlib and contribute to the shared code base and
> documentation. Yes, this places a burden on CPython, but in the long
> term in benefits *all* of the pro
Hi,
I asked one year ago if we should drop OS/2 support: Andrew MacIntyre,
our OS/2 maintainer, answered:
http://mail.python.org/pipermail/python-dev/2010-April/099477.html
Extract: << The 3.x branch needs quite a bit of work on OS/2 to
deal with Unicode, as OS/2 was one of the earlier OSes with
On Apr 19, 2011, at 03:25 PM, anatoly techtonik wrote:
>On Mon, Apr 18, 2011 at 3:53 PM, Barry Warsaw wrote:
>> With Martin getting ready to release 2.5.6, I think it's time to prepare a
>> 2.6.7 source-only security release.
>>
>> I'll work my way through the NEWS file and recent commits, but if
In reviewing a fix for the metaclass calculation in __build_class__
[1], I realised that PEP 3115 poses a potential problem for the common
practice of using "type(name, bases, ns)" for dynamic class creation.
Specifically, if one of the base classes has a metaclass with a
significant __prepare__()
Victor Stinner wrote:
> Hi,
>
> I asked one year ago if we should drop OS/2 support: Andrew MacIntyre,
> our OS/2 maintainer, answered:
> http://mail.python.org/pipermail/python-dev/2010-April/099477.html
>
> Extract: << The 3.x branch needs quite a bit of work on OS/2 to
> deal with Unicode, as
On Tue, 19 Apr 2011 07:06:09 +0200, Stefan Behnel wrote:
> That's what makes the PEP feel so unfair to CPython developers, because
> they are the ones who carry most of the burden of maintaining the stdlib in
> the first place, and who will most likely continue to carry it, because
> other impl
On Tue, 19 Apr 2011 10:37:41 -0400
"R. David Murray" wrote:
> On Tue, 19 Apr 2011 07:06:09 +0200, Stefan Behnel wrote:
> > That's what makes the PEP feel so unfair to CPython developers, because
> > they are the ones who carry most of the burden of maintaining the stdlib in
> > the first place
On Tue, 19 Apr 2011 12:01:44 +0200, Stefan Behnel wrote:
> A related question is: when other Python VM projects try to port a given C
> module, would they actually invest the time to write a pure Python version
> that may or may not run within acceptable performance bounds for them, or
> would
On Tue, 19 Apr 2011 14:29:24 +0200, Maciej Fijalkowski wrote:
> > Once this move is made/accepted, I would expect the other
> > implementation to rapidly move away from their custom implementations
> > of the stdlib and contribute to the shared code base and
> > documentation. Yes, this places a b
Hi,
summary:
Fix a few hyphens in argparse.rst.
- :synopsis: Command-line option and argument parsing library.
+ :synopsis: Command-line option and argument-parsing library.
I believe that change should be reverted. “argument parsing library”
is
a noun determined (qualified) by ano
On Apr 19, 2011, at 10:36 AM, M.-A. Lemburg wrote:
> Victor Stinner wrote:
>> Hi,
>>
>> I asked one year ago if we should drop OS/2 support: Andrew MacIntyre,
>> our OS/2 maintainer, answered:
>> http://mail.python.org/pipermail/python-dev/2010-April/099477.html
>>
>> Extract: << The 3.x branch
Doug Hellmann wrote:
>
> On Apr 19, 2011, at 10:36 AM, M.-A. Lemburg wrote:
>
>> Victor Stinner wrote:
>>> Hi,
>>>
>>> I asked one year ago if we should drop OS/2 support: Andrew MacIntyre,
>>> our OS/2 maintainer, answered:
>>> http://mail.python.org/pipermail/python-dev/2010-April/099477.html
>
Le mardi 19 avril 2011 à 15:20 -0400, Doug Hellmann a écrit :
> > The Python core team is not really representative of the Python
> > community users, so I think this needs a different approach:
> >
> > Instead of simply deprecating OSes without notice to the general
> > Python community, how abou
On Tue, 19 Apr 2011 15:20:13 -0400
Doug Hellmann wrote:
>
> Victor, if you want to post the "call for support" to Python Insider, let me
> know off list and I will set you up with access.
Doesn't it have more chances of succeeding if posted to
comp.lang.python, simply?
Regards
Antoine.
> Well, not "remove" directly, but plan to remove it using the PEP 11
> procedure (mark OS/2 and VMS as unsupported, and remove the code in
> Python 3.4).
I think the PEP 11 procedure is just right for this. It *is* a call
for maintainers, so if any user is interested in ongoing support,
they shou
23 matches
Mail list logo
