Guido van Rossum added the comment:
This patch doesn't apply cleanly any more. Is it easy to update?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
I'm also looking for some example code that would show clearly the kind of
speedup we're talking about.
--
___
Python tracker
<http://bugs.python.o
Guido van Rossum added the comment:
If there are a lot of Android issue maybe you could get a tracker manager
to add a new keyword or category or whatever?
--
___
Python tracker
<http://bugs.python.org/issue26
Guido van Rossum added the comment:
OK, I get it. I think it would be really helpful if issue 26110 was updated,
reviewed and committed -- it sound like a good idea on its own, and it needs
some burn-in time due to the introduction of two new opcodes. (That's
especially important
Guido van Rossum added the comment:
All sounds good. Glad the issue of long-running loops is at least on your
radar.
--
___
Python tracker
<http://bugs.python.org/issue26
Guido van Rossum added the comment:
Serhiy, I'm happy to help, but I'm not sure what you're asking me to do. Decide
between different patches? I can't even repro the issue.
--
___
Python tracker
<http://bug
Guido van Rossum added the comment:
To me, the best rhythm has always been (*args, **kwds).
--
___
Python tracker
<http://bugs.python.org/issue25770>
___
___
Pytho
Guido van Rossum added the comment:
Can't you easily write such a policy yourself? Why does it have to be a
standard part of asyncio?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
And by "safely" I mean that I don't mind if some code breaks when they upgrade
to a new feature release.
FWIW the code most likely to break is code that wraps these functions with an
iden
Guido van Rossum added the comment:
I think such a change can be safely made in a feature release (say 3.6) without
further deprecation. But not in a bugfix release (say 3.5.2).
--
___
Python tracker
<http://bugs.python.org/issue25
Guido van Rossum added the comment:
Sadly it's been a very long time since I wrote that code and I don't recall
much about it. I presume there was a good reason for not to do it in
_PyType_Lookup(), but who knows -- maybe the oroginal approach was just too
naive and nobody cared? I
Guido van Rossum added the comment:
> Guido's decision on similar issue25628 is that changing keyword-or-positional
> parameters to keyword-only is safe and can be made without deprecation.
> If we started the deprecation period in 3.4, we could finish it in 3.6.
That makes lit
Guido van Rossum added the comment:
But the problem isn't limited to format()... Why would format() be special?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Honestly I think it's pretty crazy and out there to have multiple event
loops in the same thread. That feels like an anti-pattern inspired by some
other event loop APIs (in other languages) that encourage this. But asyncio
was not designed for
Guido van Rossum added the comment:
Probably.
--
___
Python tracker
<http://bugs.python.org/issue26906>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
FWIW asyncio's own test suite makes sure that the loop is indeed passed
everywhere by setting the default loop to None. If a library chooses to
pass the loop around like this it should structure its tests the sam
Guido van Rossum added the comment:
Because the data structure that defines a type is just data, and at some
point PyType_Ready() must be called. The question is how to do this, given
that nobody can (or needs to) produce a definitive list of all types
Guido van Rossum added the comment:
PS. If you have something you sometimes want to run synchronously and
sometimes as a coroutine, you probably need to refactor it somehow.
--
___
Python tracker
<http://bugs.python.org/issue26
Guido van Rossum added the comment:
No, that specifically sounds like asking for trouble to me. You don't know
what else that coroutine is waiting for, and it may be waiting for some I/O
whose socket is registered with the other event loop. Since the other event
loop won't make progr
Changes by Guido van Rossum :
--
assignee: docs@python -> gvanrossum
nosy: +gvanrossum
___
Python tracker
<http://bugs.python.org/issue26982>
___
___
Python-
Guido van Rossum added the comment:
Instead of starting a new event loop, you should figure out a way to wait
for an event in the existing loop. IIUC that loop runs in a different
thread -- I think you can solve this by using a threading.Event that you
set from a wrapper coroutine running in
Guido van Rossum added the comment:
Still no green light. Ilya just seems to want something misguided.
--
___
Python tracker
<http://bugs.python.org/issue26
Guido van Rossum added the comment:
Yury, what do you think of this yourself? Maybe you can explain it better
than Ilya?
--
___
Python tracker
<http://bugs.python.org/issue26
Guido van Rossum added the comment:
As long as there are still things you find confusing about asyncio's model,
you should probably consider yourself unqualified to start proposing new
features...
--
___
Python tracker
<http://bugs.py
Guido van Rossum added the comment:
Reopening as we need to rename the path attribute to __fspath__ once Brett's
PEP is accepted (which will be soon).
https://github.com/brettcannon/path-pep/blob/master/pep-0NNN.rst
The 3.4 and 3.5 versions of this should probably just be reversed b
Guido van Rossum added the comment:
Presumably. :-(
--
___
Python tracker
<http://bugs.python.org/issue22970>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Yury can you take this on?
--
assignee: -> yselivanov
___
Python tracker
<http://bugs.python.org/issue22970>
___
___
Py
Guido van Rossum added the comment:
Ow, that's bad. :-(
Great job reducing this to a minimal repro!
I'm guessing it's got to do with registration. I'll try to figure out how to
fix it; the fix should appear in Python 3.5.2.
--
assi
Guido van Rossum added the comment:
Simpler repro:
from collections import UserList
from typing import Sequence
class MyList(UserList, Sequence):
pass
isinstance(None, Sequence)
No progress yet in understanding. :-(
--
___
Python tracker
<h
Guido van Rossum added the comment:
See also https://github.com/python/mypy/issues/1546 -- possibly it's the same
issue.
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Actually, see https://github.com/python/typing/issues/222 instead.
--
___
Python tracker
<http://bugs.python.org/issue27
Guido van Rossum added the comment:
Thanks to Kalle Tuure for the fix!
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
versions: +Python 3.6
___
Python tracker
<http://bugs.python.or
Guido van Rossum added the comment:
PEP 519 is accepted now. We need to revert the commits from
http://bugs.python.org/issue22570#msg257634
--
___
Python tracker
<http://bugs.python.org/issue22
Guido van Rossum added the comment:
And those from http://bugs.python.org/issue22570#msg257632 (these are the
actual code -- the others were the docs).
--
___
Python tracker
<http://bugs.python.org/issue22
Guido van Rossum added the comment:
Done. The revs are 90e58a77d386, 97198545e6c3, ade839421b8f.
--
resolution: out of date -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Guido van Rossum added the comment:
It's the name of the UNIX domain socket.
--
___
Python tracker
<http://bugs.python.org/issue26980>
___
___
Python-bugs-l
Guido van Rossum added the comment:
The patch no longer applies cleanly. I had to do "hg up -r ac0d6c09457e" to get
a checkpoint to which it applies. (But I'm not sure at what point that landed
me.)
--
___
Python tracker
<http
Guido van Rossum added the comment:
I recall discussing this before (maybe on the tulip list). I am firmly against.
It is a slippery slope -- why inspect a partial but not a lambda? Plus there is
no use case.
--
___
Python tracker
<h
Guido van Rossum added the comment:
Yeah, your "add event handler" routine shouldn't be so picky to insist that
iscoroutinefunction() returns True. It should just call the thing and verify
that it has returned a coroutine object (asyncio.iscoroutine()).
--
resolution
Guido van Rossum added the comment:
Does it also have that error if you add `asyncio.get_event_loop().close()` to
the end of the program?
Can you figure out what the value of `sig` and `handler` are in the traceback?
My gut feeling tells me this is due to `signal.default_int_handler` being
Guido van Rossum added the comment:
So this is still strange. When you do this, does it give the same exception?
>>> import signal
>>> signal.signal(signal.SIGCHLD, signal.SIG_DFL)
--
___
Python tracker
<http://bugs.
Guido van Rossum added the comment:
Looking for code reviewers!
--
stage: -> patch review
type: -> enhancement
___
Python tracker
<http://bugs.python.org/i
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue22936>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
I think it's pretty silly to have math.py. And why would there be a
pure-Python implementation of factorial() (like anybody is ever going to
use that) instead of example implementations of sin() etc.? Please don't go
down this path for this particu
Guido van Rossum added the comment:
This makes some sense, but it's easy to work around -- just call
create_server() multiple times, once for each host. Why does that not work for
you?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
So it sounds like you already have a patch in mind... Can you work on it and
upload it? (It's open source -- you get to make it yourself. :-)
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Yeah, the stack track makes me suspect http://bugs.python.org/issue17911
--
nosy: +gvanrossum
___
Python tracker
<http://bugs.python.org/issue23
Guido van Rossum added the comment:
Could use a test. Hopefully Victor can do a thorough review.
On Tue, Mar 10, 2015 at 12:20 PM, Sebastien Bourdeauducq <
rep...@bugs.python.org> wrote:
>
> Sebastien Bourdeauducq added the comment:
>
> See attached.
>
> --
&g
Guido van Rossum added the comment:
Are we all in agreement that it's probably somehow running out of memory?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
So what do you make of this?
PyObject_GC_Malloc(unsigned __int64 basicsize=4046951880)
That's nearly 4 GB. I somehow doubt your app is actually trying to allocate
that much memory -- maybe the type object a few lines below in the stack is
overwritte
Guido van Rossum added the comment:
I'm a little surprised you didn't get pushback from asyncio (i.e. Victor). We
try to keep the source identical across releases while asyncio is in
provisional mode (i.e. until 3.5 is released).
--
nosy: +gvanros
Guido van Rossum added the comment:
Looks like a valid bug report, I like the test you provided, and the fix seems
on the right track. Comments on the fix:
- I'd really like to see a rietveld diff for both patches.
- Are there other places where a cancellation can have a similar effect?
Guido van Rossum added the comment:
Make sense. I'll be waiting for your updated patch. Thanks for both the bug
report and the fix!
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Yeah, I'd like to see it restored in asyncio. It seems to be just one file
that's currently out of sync with the tulip "upstream" repo.
On Mon, Mar 30, 2015 at 10:38 AM, Serhiy Storchaka
wrote:
>
> Serhiy Storchaka added the com
Guido van Rossum added the comment:
Thanks!
On Mon, Mar 30, 2015 at 12:26 PM, Roundup Robot
wrote:
>
> Roundup Robot added the comment:
>
> New changeset e881444f078f by Serhiy Storchaka in branch 'default':
> Partially revert 3603bae63c13 (issue23326) for asyncio
Guido van Rossum added the comment:
I'm sorry, I don't have time to review this (and it's subtle enough that I
don't want to approve it without understanding).
Maybe Victor understands?
--
___
Python tracker
<http://bug
Guido van Rossum added the comment:
LGTM.
On Apr 7, 2015 1:23 AM, "STINNER Victor" wrote:
>
> New submission from STINNER Victor:
>
> According to the issue #23618, when connect() fails with EINTR, retrying
> connect() may only work on some platforms. To have a re
Guido van Rossum added the comment:
This needs a code patch. But it can only be fixed for 3.5.
On Apr 7, 2015 11:21 AM, "Steve Dougherty" wrote:
>
> Steve Dougherty added the comment:
>
> Any word on either changing the documentation to match the behaviour or
Guido van Rossum added the comment:
Here's a unittest by Christie Wilson for this issue.
--
keywords: +patch
nosy: +gvanrossum
Added file: http://bugs.python.org/file38900/fix_issue_21511.diff
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Fixed, and removing the dependency on issue 18022. Thanks Christie!
--
dependencies: -Inconsistency between quopri.decodestring() and
email.quoprimime.decode()
resolution: -> fixed
___
Python tracker
&l
Guido van Rossum added the comment:
I think we left this unfinished. I think it would be best if we added a sock
parameter (like for create_server()) but also added reuse_address and
reuse_port parameters, treated similarly like the one on create_server(), and
added a reuse_port parameter to
Guido van Rossum added the comment:
Did anyone look at this yet? The ultimate deadline would be May 24 (beta 1).
But making alpha 4 (April 19) would be better.
--
___
Python tracker
<http://bugs.python.org/issue22
New submission from Guido van Rossum:
I'm creating a release blocker placeholder issue for PEP 484. I think we're
going to miss alpha 4 but I am expecting to make beta 1 (and Mark Shannon, the
BDFL-Delegate has promised to work within this schedule). Of course it's
possible th
Guido van Rossum added the comment:
Uh, wait. Who's patching anything? That breaks the warranty.
--
___
Python tracker
<http://bugs.python.org/issue24004>
___
___
Guido van Rossum added the comment:
It's missing tests. :-)
Otherwise looks quite sensible.
Also, shouldn't you override __subclasshook__ so you don't inherit it from
Iterator?
--
___
Python tracker
<http://bugs.pyt
Guido van Rossum added the comment:
Is it an option to leave inspect alone? Its definition and use of generators is
very focused on the builtin implementation.
Although this means that code that wants to do the right thing but also be
backwards compatible has to use something like
```
def
Guido van Rossum added the comment:
Realistically only Cython will care much about this, so I'm okay if Cython just
monkeypatches the collections package.
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
It would be unacceptable if print(b) were to raise an exception. The reason the
transitional period is long is just that people are still porting Python 2 code.
--
assignee: -> gvanrossum
status: pending ->
Guido van Rossum added the comment:
I'm with Raymond.
--
___
Python tracker
<http://bugs.python.org/issue24018>
___
___
Python-bugs-list mailing list
Unsubscr
Guido van Rossum added the comment:
We didn't do this originally because the 3.4 SSL module didn't have this
functionality (or maybe it was 3.3 that didn't have this) but now that we do
have it I'd be very happy if you could implement this!
I'm not sure what the rig
Changes by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<http://bugs.python.org/issue24017>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Does the cpython test runner have this? Might be nice there. Not sure if
the default test runner is something to extend at this point. Eveybody is
using py.test anyway...
On Monday, April 27, 2015, Ned Deily wrote:
>
> Changes by Ned
Guido van Rossum added the comment:
It's trivial to add to a single test or even a single TestCase subclass, yes.
The use case is more that you have a ton of tests and you suspect there's a
problem due to GC. Being able to call gc.collect() after each test through the
flip of a fla
Guido van Rossum added the comment:
That sounds like a good plan for the top-level APIs.
But I think we may need to think about low-level APIs that handle Transports
and Protocols as well.
The design I had been thinking of does not do any socket-level manipulation (in
fact it doesn't ca
Guido van Rossum added the comment:
Looks like Antoine drew the same diagram but quicker. :-)
Regarding the waiter arg, you can leave that None if you don't need it. It is
intended to give the caller a way to block (using event loop machinery) until
the connection is ready. But if your c
Guido van Rossum added the comment:
You can't just drop the middle sentence. Awkward though it is, it is attempting
to describe that the generator object controls suspension and resumption of the
stack frame representing execution of the generator function&#
Guido van Rossum added the comment:
I think we can continue this discussion *after* the PEP's been accepted.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue24108>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Thanks for the review Thomas! And yes, that's what I meant. :-)
--
___
Python tracker
<http://bugs.python.org/i
Guido van Rossum added the comment:
Yeah, looks good -- Łuke, can you commit this?
--
___
Python tracker
<http://bugs.python.org/issue24018>
___
___
Python-bug
Changes by Guido van Rossum :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue24088>
___
___
Python-bugs-
Guido van Rossum added the comment:
Yeah, but the docs don't need to be committed in time for beta 1. The
source code should go in ASAP, especially since the PEP 492 changes will
have to be merged in on top of them. @Thomas: which Monday were you
shooting for? I had hoped yesterday...
O
Guido van Rossum added the comment:
(To clarify, the PEP itself probably serves as enough documentation in the
interim.)
On Tue, May 5, 2015 at 4:47 PM, Guido van Rossum wrote:
> Yeah, but the docs don't need to be committed in time for beta 1. The
> source code should go in ASAP,
Guido van Rossum added the comment:
Thanks Benjamin!
On May 5, 2015 5:17 PM, "Benjamin Peterson" wrote:
>
> Benjamin Peterson added the comment:
>
> a65f685ba8c0
>
> --
> resolution: -> fixed
> status: open -> closed
>
> __
Guido van Rossum added the comment:
Well that would break a lot of code...
On May 5, 2015 5:18 PM, "STINNER Victor" wrote:
>
> STINNER Victor added the comment:
>
> Would it be possible to push the first part of the implementation (without
> __future__) just to unbl
Guido van Rossum added the comment:
I think it's fine. It collects all the keys and values and then calls
BUILD_MAP (a new opcode), rather than calling STORE_MAP for each key/value
pair. I think this is a reasonable strategy for compiling a dict display.
On Thu, May 7, 2015 at 11:40 AM, J
Guido van Rossum added the comment:
I think you could help by (a) reviewing what's there, and (b) helping with
the implementation of __future__.
On Thu, May 7, 2015 at 1:16 PM, Yury Selivanov
wrote:
>
> Yury Selivanov added the comment:
>
> > You sure can! Take it, dep
Guido van Rossum added the comment:
Or, if it's perfect (or good enough :-), just check it in.
On Thu, May 7, 2015 at 1:18 PM, Guido van Rossum
wrote:
>
> Guido van Rossum added the comment:
>
> I think you could help by (a) reviewing what's there, and (b) helping with
&
Guido van Rossum added the comment:
Ask Yury if he'll commit it for you. It's ready.
--
___
Python tracker
<http://bugs.python.org/issue24018>
___
___
Guido van Rossum added the comment:
Fixed.
On Fri, May 8, 2015 at 10:28 PM, Stefan Behnel
wrote:
>
> Stefan Behnel added the comment:
>
> Thanks! Minor grouch: it should say "collections.*abc*.Generator" in the
> NEWS entry.
>
> --
>
> ___
Guido van Rossum added the comment:
Thank you Yury! You are a coding machine.
On Mon, May 11, 2015 at 8:06 PM, Yury Selivanov
wrote:
>
> Yury Selivanov added the comment:
>
> Guido, Nick, Victor,
> Thanks for your reviews and guidance! The patch has been committed to the
&
Guido van Rossum added the comment:
BTW, a shout out to Nick for doing most of the review for this monster patch.
Thanks!
--
___
Python tracker
<http://bugs.python.org/issue24
New submission from Guido van Rossum:
The special methods __complex__ and __bytes__ are not present on the
corresponding builtin types. Compare this to __int__ and __float__, which do
exist on int and float, respectively. Should we add the eponymous methods to
complex and bytes?
(This came
Guido van Rossum added the comment:
I am going to commit this (or something very close to it) unless I hear an
explicit rejection notice from Mark Shannon. Off-list he's promised he'll
approve the PEP provisionally, and the window for beta 1 is closing. It's
better to iterate t
Guido van Rossum added the comment:
New patch.
--
Added file: http://bugs.python.org/file39463/pep484.diff
___
Python tracker
<http://bugs.python.org/issue23
Guido van Rossum added the comment:
This was committed (rev 3e96d7ca3f51). I'm keeping this open because there is
more to do (see https://github.com/ambv/typehinting/labels/bug).
--
priority: release blocker -> normal
___
Python tracke
Changes by Guido van Rossum :
--
stage: -> needs patch
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue24272>
___
___
Python-bugs-
New submission from Guido van Rossum:
Would be nice if there were more docs for the typing module (PEP 484). Looking
for volunteers. (There's stuff in the PEP that can serve as a starting point.)
Note: support for isinstance() and issubclass() will be withdrawn in beta 2.
--
ass
Guido van Rossum added the comment:
I've opened a separate bug (http://bugs.python.org/issue24272) for docs.
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Thanks! Your attention to detail is appreciated.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.5
___
Python tracker
<http://bugs.python.or
5301 - 5400 of 5563 matches
Mail list logo
