cluding an
additional chunk of documentation and a unit test.
Dustin
-cut-here-
try:
from cStringIO import StringIO
except:
from StringIO import StringIO
class SpooledTemporaryFile:
"""Temporary file wrapper, specialized to switch from
Str
ications or improvements anyone has in mind,
please let me know.
Dustin
___
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
**kwargs)
return self
return wrap
else:
return rv
mylist = [1, 2, 3]
wrapcall(mylist).reverse().append(2).reverse()
assert mylist == [2, 1, 2, 3]
Dustin
___
Python-Dev mailing list
Python-Dev@python.o
post a
reasonable prototype soon (a PEP would also be in order at some point,
correct?).
Dustin
___
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
that far ahead yet. I expect #2 will
be the hardest!
Dustin
___
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
#x27;m having. Rather, I think that the new language features in
PEP 342 cry out for a batteries-included library that makes asynchronous
programming both natural and easy.
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
tify of events on the objects in a standard way.
>
> +1. This sounds like an excellent idea. It's downright
> silly having each thing that uses async I/O doing its
> own thing. There should be a standard mechanism in the
> stdlib that everything can use.
I'm workin'
being built on top of those modules,
seems to me to suggest a new "standard" implementation should be added
to the standard library.
I realize that I'm all talk and no code -- I've been busy, but I hope to
rectify the imbalance tonight.
Dustin
[1] http://mail.python.org/pipermail/
nly wait
on 64 fd's, etc.) to the application for compatibility-checking
purposes.
Thoughts?
Dustin
___
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
s a consistent syntax for microthreaded code, so that I
could write my function once and run it in *all* of those circumstances.
Dustin
P.S. For the record -- I've written lots of other apps in Twisted with
great success; this one just wasn't a good fit.
___
andardizing* that
style so that it's the same in Twisted, my library, and anyone else's
library that cares to follow the standard?
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Uns
ph. I think I'm most unclear
about the meaning of "The 'threading' approach to asynchronous I/O"?
Its opposite ("separating asynchronous I/O from threading") doesn't
illuminate it much more. Could you elaborate?
Dustin
__
threading" in a completely
> different way than usual here, which may be causing some
> confusion.
According to subsequent clarification, the kind of IO Nick is talking
about is the sort of thing described recently on kerneltrap:
http://kerneltrap.org/node/7728
(althoug
lso looks a lot like the current syntax, but (unless I'm
mistaken) ExceptionClass will be instantiated immediately right now. It
seems best not to change the semantics of existing syntax if not
necessary.
I've been snoozing though this conver
ct's idea of maintainers
(although in Gentoo maintainers must be full developers).
Dustin
___
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 Tue, Mar 06, 2007 at 01:51:41PM -0600, [EMAIL PROTECTED] wrote:
>
> dustin> In summary, create a layer of volunteer, non-committing
> dustin> maintainers for specific modules who agree to do in-depth
> dustin> analysis of patches for their areas of expertise,
>to do so, leaving my patch to rot only harms CPython, not me.
Miguel, last week there was a lengthy conversation on this list on this
exact topic. Your point of view, which I hold to be very common, came
up a few times, but thanks for stating it so clearly!
Dustin
P.S. Please note I am *
immediately (to prevent other applications from
modifying your temporary file). NamedTemporaryFile is inteded for use
when you need access to the file by filename during the lifetime of the
file. In either case, when the object goes, the file should too.
Dustin
__
t, I don't see
any contradiction here, and I don't see any reason to spend time
updating the style guide.
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.py
patches, as
Python does. Spurious whitespaces changes in the repo will generate
patch rejections that will drive both maintainers (as they check in a
patch) and submitters (as they try to refresh patches against head) mad.
I'm very much interested in VC systems *not* driving develop
is counter to the Subversion
Way.
Also, you could accomplish what you want (a locked branch) with a
pre-commit hook that just scans for paths in that branch.
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
emote repository I've ever
accessed.
Dustin
___
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
roblem with this proposal, but I consider the snippet
above to be fairly obscure Python already; the requirement to call
g.close() is not a great burden on someone capable of using g.send() et
al.
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http
Readline and
affects both Linux and macOS.
Thanks,
Dustin
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https
make sure that tracebacks
looked reasonable, filtering out scheduler code[1]. I haven't looked
closely at Tulip to see if that's a problem. Most of the "noise" in the
tracebacks came from the lack of 'yield from', so it may not be an issue at
all.
Dustin
[1]
an type 'php.net/array_search' to
try to find out whether the needle comes before or after the haystack.
Dustin
___
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
worked on this subject:
http://www.usenix.org/events/usenix01/full_papers/beazley/beazley_html/index.html
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/m
using 'write' in the name.
FWIW, "half-closed" is, IMHO, a well-known term. It's not just a Twisted thing.
Either name is better than "shutdown"!
Dustin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
28 matches
Mail list logo
