On Dec 24, 2012 11:44 PM, "Brian Curtin" wrote:
>
> On Mon, Dec 24, 2012 at 7:42 AM, anatoly techtonik
wrote:
> > What should I do in case Eric lost interest after his GSoC project for
PSF
> > appeared as useless for python-dev community? Should I rewrite the
proposal
> > from scratch?
>
> Before
On Mon, Dec 24, 2012 at 7:42 AM, anatoly techtonik wrote:
> What should I do in case Eric lost interest after his GSoC project for PSF
> appeared as useless for python-dev community? Should I rewrite the proposal
> from scratch?
Before you attempt that, start by trying to have a better attitude
t
Hey,
Anatoly, you are free to modify the PEP and code. I do not have any
plans to work on this right now.
Eric
On Mon, Dec 24, 2012 at 04:42:20PM +0300, anatoly techtonik wrote:
> What should I do in case Eric lost interest after his GSoC project for PSF
> appeared as useless for python-dev comm
What should I do in case Eric lost interest after his GSoC project for PSF
appeared as useless for python-dev community? Should I rewrite the proposal
from scratch?
On Thu, Dec 20, 2012 at 11:18 PM, Brett Cannon wrote:
> You cannot rewrite an existing PEP if you are not one of the original
> own
On Fri, Dec 21, 2012 at 6:46 AM, Brett Cannon wrote:
>
> On Thu, Dec 20, 2012 at 7:35 PM, Chris Jerdonek
> wrote:
>>
>> I don't disagree that he shouldn't have cross-posted. I was just
>> pointing out that the language should be clarified. What's confusing
>> is that the current language implie
Please stop copying me on this thread.
Thanks,
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
On Thu, Dec 20, 2012 at 7:35 PM, Chris Jerdonek wrote:
> On Thu, Dec 20, 2012 at 1:12 PM, Brett Cannon wrote:
> >
> > On Thu, Dec 20, 2012 at 3:55 PM, Chris Jerdonek <
> chris.jerdo...@gmail.com>
> > wrote:
> >>
> >> On Thu, Dec 20, 2012 at 12:18 PM, Brett Cannon
> wrote:
> >> >
> >> > And pleas
On Thu, Dec 20, 2012 at 1:12 PM, Brett Cannon wrote:
>
> On Thu, Dec 20, 2012 at 3:55 PM, Chris Jerdonek
> wrote:
>>
>> On Thu, Dec 20, 2012 at 12:18 PM, Brett Cannon wrote:
>> >
>> > And please do not CC the peps mailing list on discussions. It should
>> > only be
>> > used to mail in new PEPs
On Thu, Dec 20, 2012 at 3:55 PM, Chris Jerdonek wrote:
> On Thu, Dec 20, 2012 at 12:18 PM, Brett Cannon wrote:
> >
> > And please do not CC the peps mailing list on discussions. It should
> only be
> > used to mail in new PEPs or acceptable patches to PEPs.
>
> PEP 1 should perhaps be clarified i
On Thu, Dec 20, 2012 at 12:18 PM, Brett Cannon wrote:
>
> And please do not CC the peps mailing list on discussions. It should only be
> used to mail in new PEPs or acceptable patches to PEPs.
PEP 1 should perhaps be clarified if the above is the case.
Currently, PEP 1 says all PEP-related e-mail
You cannot rewrite an existing PEP if you are not one of the original
owners, nor can you add yourself as an author to a PEP without permission
from the original authors.
And please do not CC the peps mailing list on discussions. It should only
be used to mail in new PEPs or acceptable patches to
On Dec 19, 2012, at 7:46 PM, anatoly techtonik wrote:
>
>> On *nix it really shouldn't be select. select cannot wait upon a file
>> descriptor whose value is greater than FD_SETSIZE, which means it sets a
>> hard (and small) limit on the number of things that a process which wants to
>> use
On Thu, Dec 20, 2012 at 3:47 AM, Glyph wrote:
>
> On Dec 19, 2012, at 2:14 PM, anatoly techtonik
> wrote:
>
> On Sun, Dec 9, 2012 at 7:14 AM, Glyph wrote:
>
>> On Dec 7, 2012, at 5:10 PM, anatoly techtonik
>> wrote:
>>
>> What about reading from other file descriptors? subprocess.Popen allows
Please stop copying me on this thread.
Thanks,
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
On Dec 19, 2012, at 2:14 PM, anatoly techtonik wrote:
> On Sun, Dec 9, 2012 at 7:14 AM, Glyph wrote:
> On Dec 7, 2012, at 5:10 PM, anatoly techtonik wrote:
>
>> What about reading from other file descriptors? subprocess.Popen allows
>> arbitrary file descriptors to be used. Is there any pr
On Sun, Dec 9, 2012 at 7:17 AM, Gregory P. Smith wrote:
> I'm really not sure what this PEP is trying to get at given that it
> contains no examples and sounds from the descriptions to be adding a
> complicated api on top of something that already, IMNSHO, has too much it
> (subprocess.Popen).
>
On Sun, Dec 9, 2012 at 7:14 AM, Glyph wrote:
> On Dec 7, 2012, at 5:10 PM, anatoly techtonik wrote:
>
> What about reading from other file descriptors? subprocess.Popen allows
>> arbitrary file descriptors to be used. Is there any provision here for
>> reading and writing non-blocking from or
On Dec 8, 2012, at 8:37 PM, Gregory P. Smith wrote:
> Is twisted's spawnProcess thread safe and async signal safe by using
> restricted C code for everything between the fork() and exec()? I'm not
> familiar enough with the twisted codebase to find things easily in it but I'm
> not seeing su
On Sat, Dec 8, 2012 at 8:14 PM, Glyph wrote:
>
> On Dec 7, 2012, at 5:10 PM, anatoly techtonik wrote:
>
> What about reading from other file descriptors? subprocess.Popen allows
>> arbitrary file descriptors to be used. Is there any provision here for
>> reading and writing non-blocking from o
I'm really not sure what this PEP is trying to get at given that it
contains no examples and sounds from the descriptions to be adding a
complicated api on top of something that already, IMNSHO, has too much it
(subprocess.Popen).
Regardless, any user can use the stdout/err/in file objects with th
On Dec 7, 2012, at 5:10 PM, anatoly techtonik wrote:
> What about reading from other file descriptors? subprocess.Popen allows
> arbitrary file descriptors to be used. Is there any provision here for
> reading and writing non-blocking from or to those?
>
> On Windows it is WriteFile/ReadFil
On Tue, Sep 15, 2009 at 9:24 PM, wrote:
> On 04:25 pm, eric.pru...@gmail.com wrote:
>
>> I'm bumping this PEP again in hopes of getting some feedback.
>>
>
This is useful, indeed. ActiveState recipe for this has 10 votes, which is
high for ActiveState (and such hardcore topic FWIW).
> On Tue, S
On 04:25 pm, eric.pru...@gmail.com wrote:
I'm bumping this PEP again in hopes of getting some feedback.
Thanks,
Eric
On Tue, Sep 8, 2009 at 23:52, Eric Pruitt
wrote:
PEP: 3145
Title: Asynchronous I/O For subprocess.Popen
Author: (James) Eric Pruitt, Charles R. McCreary, Josiah Carlson
Type:
Hello,
I would like to know if your approach is based on Python 2.x or 3.x.
Python 3.x has new API provisions, in the I/O layer, for non-blocking I/O
and it would be nice if your work could fit in that framework.
> >Popen can be made to act like a file by simply
> >using the methods att
On Tue, Sep 15, 2009 at 12:25:35PM -0400, Eric Pruitt wrote:
> A search for "python asynchronous subprocess" will turn up numerous
> accounts of people
IMHO there is no need to refer to a search. It'd be enough to say "There
are many people...".
> kernel 32 DLL
Why not just name it kernel3
I'm bumping this PEP again in hopes of getting some feedback.
Thanks,
Eric
On Tue, Sep 8, 2009 at 23:52, Eric Pruitt wrote:
> PEP: 3145
> Title: Asynchronous I/O For subprocess.Popen
> Author: (James) Eric Pruitt, Charles R. McCreary, Josiah Carlson
> Type: Standards Track
> Content-Type: text/p
On Tue, Sep 8, 2009 at 19:56, Benjamin Peterson wrote:
> 2009/9/7 Eric Pruitt :
>> Hello all,
>>
>> I have been working on adding asynchronous I/O to the Python
>> subprocess module as part of my Google Summer of Code project. Now
>> that I have finished documenting and pruning the code, I present
Alright, I will re-submit with the contents pasted. I never use double
backquotes as I think them rather ugly; that is the work of an editor
or some automated program in the chain. Plus, it also messed up my
line formatting and now I have lines with one word on them... Anyway,
the contents of PEP 3
2009/9/7 Eric Pruitt :
> Hello all,
>
> I have been working on adding asynchronous I/O to the Python
> subprocess module as part of my Google Summer of Code project. Now
> that I have finished documenting and pruning the code, I present PEP
> 3145 for its inclusion into the Python core code. Any an
Hello all,
I have been working on adding asynchronous I/O to the Python
subprocess module as part of my Google Summer of Code project. Now
that I have finished documenting and pruning the code, I present PEP
3145 for its inclusion into the Python core code. Any and all feedback
on the PEP (http://
30 matches
Mail list logo
