On Tue, May 5, 2015 at 3:25 PM, Yury Selivanov
wrote:
>
> Yes, there is no other popular event loop for 3.4 other
> than asyncio, that uses coroutines based on generators
> (as far as I know).
>
Tornado supports Python 3.4 and uses generator-based coroutines. We use
`yield` instead of `yield fro
On Tue, May 5, 2015 at 1:39 PM, Paul Moore wrote:
>
> It would probably be helpful to have a concrete example of a basic
> event loop that did *nothing* but schedule tasks. No IO waiting or
> similar, just scheduling. I have a gut feeling that event loops are
> more than just asyncio, but without
On Tue, Dec 12, 2017 at 12:34 PM Yury Selivanov
wrote:
> Hi,
>
> This is a new proposal to implement context storage in Python.
>
> It's a successor of PEP 550 and builds on some of its API ideas and
> datastructures. Contrary to PEP 550 though, this proposal only focuses
> on adding new APIs an
On Sun, Dec 17, 2017 at 2:49 PM Yury Selivanov
wrote:
> > One caveat based on Tornado's experience with stack_context: There are
> times
> > when the automatic propagation of contexts won't do the right thing (for
> > example, a database client with a connection pool may end up hanging on
> to
>
On Mon, Dec 18, 2017 at 8:37 PM Yury Selivanov
wrote:
> > 3. The connection pool has a queue, and creates a task for each
> connection to serve requests from that queue. Naively, each task could
> inherit the context of the request that caused it to be created, but the
> task would outlive the re
I agree wholeheartedly with the sentiment behind this PEP, but I have
concerns about the implementation. If we introduce new APIs into the ssl
module then we will see packages and applications that depend on Python
2.7.7+, just like with the introduction of bool in 2.2.1. This will be a
mess unle
On Sat, Mar 22, 2014 at 7:08 PM, Nick Coghlan wrote:
>
> The issue isn't really the ssl module itself - it's the other modules
> that *depend* on the ssl module (like httplib, urllib, poplib, ftplib,
> imaplib). You could technically try to monkeypatch or shadow the
> stdlib ssl module from a thi
On Sat, Mar 22, 2014 at 8:55 PM, Nick Coghlan wrote:
> What we have essentially found is that where we could basically get
> away with an 18 month update cycle for improved network security
> support (extended out to a few years by certain major platform
> vendors), that approach *isn't* working
On Mon, Mar 24, 2014 at 4:44 AM, Nick Coghlan wrote:
>
> On 24 Mar 2014 15:25, "Chris Angelico" wrote:
>
> > As has already been pointed out, this can already happen, but in an
> > ad-hoc way. Making it official or semi-official would mean that a
> > script written for Debian's "Python 2.7.10" w
On Wed, Mar 26, 2014 at 6:02 PM, Antoine Pitrou wrote:
> On Wed, 26 Mar 2014 23:57:27 +0200
> Marko Rauhamaa wrote:
> > Antoine Pitrou :
> >
> > > Marko Rauhamaa wrote:
> > >> In my experience, networking entities typically start a timer at each
> > >> interaction and cancel the pending one. So
On Mon, Jun 3, 2013 at 1:20 AM, Donald Stufft wrote:
> As of right now, as far as I can tell, Python does not validate HTTPS
> certificates by default. As far as I can tell this is because there is no
> guaranteed certificates available.
>
> So I would like to propose that CPython adopt the Mozil
Trying to transfer github comments from
https://github.com/python/peps/pull/272#pullrequestreview-41388700:
I said:
> Tornado has been doing TLS in an event-loop model in python 2.5+ with
just wrap_socket, no MemoryBIO necessary. What am I missing? MemoryBIO
certainly gives some extra flexibility,
The PEP's rationale is now "This PEP will help facilitate the future
adoption
of :pep:`543` across all supported Python versions, which will improve
security
for both Python 2 and Python 3 users."
What exactly are these security improvements? My understanding (which may
well be incorrect) is that
13 matches
Mail list logo
