On Mon, Mar 6, 2017 at 5:57 PM, Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
> Of course, it makes sense that anything not specific to asyncio should go
> outside of asyncio.
>
> What I'm more concerned about is what the other places actually are.
> Rather than putting async variants o
> On Mar 1, 2017, at 8:47 AM, Yury Selivanov wrote:
>
>> IMHO this is a good idea*iff* the new APIs really are bound to
>> asyncio, rather than being generic across all uses of async/await.
>
> I agree. There is no need to make asynccontextmanager and
> AsyncExitStack dependent on asyncio or
This mailling list is for coordinating the development of the Python
programming language, not to be used for marketing.
Share your articles on a social network or a forum such as
reddit.com/r/python.
Le 06/03/2017 à 16:53, Yaroslav Lehenchuk a écrit :
> Hi!
>
> I like your resource. We in Djan
On 6 March 2017 at 00:39, INADA Naoki wrote:
> I prefer just "locale-aware" / "locale-independent" (application |
> library | function)
> to "locale-aware C/C++ application" / "C/C++ independent" here.
Good point, I'll fix that in the next update.
> Backporting to Python 3.6.0
> > --
Hi!
I like your resource. We in Django Stars writing a lot about Python/Django
and we would like to share our articles with other professionals and geeks.
Here are two examples of our blog content:
http://djangostars.com/blog/continuous-integration-circleci-
vs-travisci-vs-jenkins/
http://djangost
