[issue5945] PyMapping_Check returns 1 for lists

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue5945> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27485] urllib.splitport -- is it official or not?

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue27485> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32769] Add 'annotations' to the glossary

Guido van Rossum added the comment: New changeset e69657df244135a232117f692640e0568b04e999 by Guido van Rossum (Andrés Delfino) in branch '3.7': [3.7] bpo-32769: A new take on annotations/type hinting glossary entries (GH-6829) (#7127) https://github.com/python/cpyt

[issue33766] Grammar Incongruence

Guido van Rossum added the comment: I am fine with adding this to the docs. But the irony of the case is that the echo command adds a newline, so the original premise (that test.py contains an invalid program) is incorrect. ;-) -- ___ Python

[issue33482] codecs.StreamRecoder.writelines is broken

Guido van Rossum added the comment: LGTM. Though sad there's no test that caught this. Could you add one. -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/is

[issue24379] Add operator.subscript as a convenience for creating slices

Guido van Rossum added the comment: Let's close it. Just because someone spent a lot of effort on a patch we don't have to accept it. -- ___ Python tracker <https://bugs.python.o

[issue27500] ProactorEventLoop cannot open connection to ::1

Guido van Rossum added the comment: Somebody please submit a PR so this can be fixed in 3.7.1 and the fix can be backported to 3.6.7. -- ___ Python tracker <https://bugs.python.org/issue27

[issue24954] No way to generate or parse timezone as produced by datetime.isoformat()

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue24954> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33346] Syntax error with async generator inside dictionary comprehension

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue33346> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Guido van Rossum added the comment: Yeah, that's a good idea. It was never meant for a ProcessPoolExecutor. We should warn against this in the docs right away (and backport the warning to all previous versions that have set_executor). I also support non-silent deprecation i

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Guido van Rossum added the comment: Of course, that's what I meant. -- ___ Python tracker <https://bugs.python.org/issue34075> ___ ___ Python-bugs-list m

[issue34075] asyncio: We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Guido van Rossum added the comment: I disagree. Other than subclasses of thread executor, what are you going to pass in? A mock? On Wed, Jul 11, 2018 at 7:34 AM STINNER Victor wrote: > > STINNER Victor added the comment: > > > I think we'll only allow instances of c.

[issue32046] 2to3 fix for operator.isCallable()

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue32046> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34037] asyncio: BaseEventLoop.close() shutdowns the executor without waiting causing leak of dangling threads

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue34037> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33073] Add as_integer_ratio() to int() objects

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue33073> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33073] Add as_integer_ratio() to int() objects

Guido van Rossum added the comment: I assume it's decided what to do -- it may not be easy to do it, but I wouldn't call it controversial at this point. -- ___ Python tracker <https://bugs.python.o

[issue26270] Support for read()/write()/select() on asyncio

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue26270> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: Serhiy, what question do you want us to answer? On Tue, Jul 17, 2018 at 5:22 AM Serhiy Storchaka wrote: > > Change by Serhiy Storchaka : > > > -- > nosy: +Mark.Shannon, gvanrossum, levkivskyi > >

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: The test fails on CPython master, so shouldn't it be removed? Don't we have a policy that all tests must pass on master? This is what I see: cpython38$ ./python.exe Lib/test/test_opcodes.py ./python.exe Lib/test/test_opco

[issue34175] typing.NamedTuple: type-checking error when "index" used as member

Guido van Rossum added the comment: > Perhaps this report should go on the mypy bug tracker rather than the Python > language tracker. Agreed. It's up to the OP to file an issue there though (hence adding @campkeith back to the nosy list). -- nosy: +campkeith resolution

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: (Serhiy: I think you meant Nuitka, not numba -- Nuitka is a Python-to-C++ compiler, and Kay is its author. Somehow he managed to confuse us all. :-) I suspect that the way `python3 -m test` runs the tests whose name you pass on the command line causes

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: Thanks for the research. At this point I'm wondering what this test is testing. There is no prescribed behavior once you delete __annotations__ from the scope -- it is not a supported operation. At the same time I don't want to add any code enfo

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: I wouldn’t object. Of course my opinion no longer matters that much. On Sat, Jul 21, 2018 at 9:33 AM Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > > Shouldn't it be deleted in 3.7+ too? The behavior tested after PR 836

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: > Did you consider my suggestion to make it a "SyntaxError" for > "del __annotations__" on a class level or even module level or at all? > Or does this go too far? That's not reasonable. __annotations__ is just an identifi

[issue32752] no information about accessing typing.Generic type arguments

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue32752> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31861] add aiter() and anext() functions to operator module

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue31861> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34508] return of non-parenthesized star-unpacking expression a SyntaxError

Guido van Rossum added the comment: I think all of these are good. Perhaps with a small change the for-loop example can allow an elegant way of iterating over multiple iterables. It would need a special case so that `for x in *a, *b:` doesn't first construct a tuple of all elements in

[issue34508] return of non-parenthesized star-unpacking expression a SyntaxError

Guido van Rossum added the comment: That's fair. Maybe we shouldn't support `for x in *a, *b:` at all then, until we've got a BDFL decision? (Because once you support it one way you can't easily change the semantics without breaking bac

[issue34508] return of non-parenthesized star-unpacking expression a SyntaxError

Guido van Rossum added the comment: > I'm surprised that they are supported in augmented assignments: `a += 1, 2, > 3`. I guess at the time it was felt that it was better to support it everywhere it *could* be supported -- and if a is a list it even makes some amount of sense.

[issue34605] Avoid master/slave terminology

Guido van Rossum added the comment: I'm closing this now. Three out of four of Victor's PRs have been merged. The fourth one should not be merged because it reflects the underlying terminology of UNIX ptys. There's a remaining quibble about "pliant children" ->

[issue32055] Reconsider comparison chaining for containment tests

Guido van Rossum added the comment: I agree that it would be less confusing if `in`/`not in` did not allow chaining, the occasional (surely very rare) useful example notwithstanding. Then again if we're going to forbid (or even discourage) unusual combinations we might also want to fro

[issue26832] ProactorEventLoop doesn't support stdin/stdout nor files with connect_read_pipe/connect_write_pipe

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue26832> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34641] Curiosity: f((a)=1) is not a syntax error -- why?

New submission from Guido van Rossum : Emily and I just discovered that f((a)=1) is accepted and compiled the same as f(a=1). This goes against the intention that keyword arguments have the syntax f(NAME=expr). I suspect that this behavior was introduced at the time we switched from

[issue32117] Tuple unpacking in return and yield statements

Guido van Rossum added the comment: Move to 3.8. -- nosy: +gvanrossum versions: +Python 3.8 -Python 3.7 ___ Python tracker <https://bugs.python.org/issue32

[issue34683] Caret positioned wrong for SyntaxError reported by ast.c

New submission from Guido van Rossum : Input file with a subtle error: a number where an assignment target is required: for 1 in []: pass Run it, it gives a SyntaxError. Note how the caret pointing to the incorrect token is position one to the left of where you'd expect it: File

[issue34683] Caret positioned wrong for SyntaxError reported by ast.c

Change by Guido van Rossum : -- nosy: +emilyemorehouse ___ Python tracker <https://bugs.python.org/issue34683> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34683] Caret positioned wrong for SyntaxError reported by ast.c

Change by Guido van Rossum : -- nosy: +eric.smith ___ Python tracker <https://bugs.python.org/issue34683> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3468] Satisfy her lovemaking desire

Change by Guido van Rossum : -- pull_requests: -8741 ___ Python tracker <https://bugs.python.org/issue3468> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32117] Tuple unpacking in return and yield statements

Guido van Rossum added the comment: Jordan, what's your GitHub account name? I hope you can check this out and make the changes I'm requesting on GitHub. -- ___ Python tracker <https://bugs.python.o

[issue30140] Binary arithmetic does not always call subclasses first

Guido van Rossum added the comment: If anyone cares, here's what I recall of the history of this feature. Originally my design was just 1. try left arg's __op__ 2. if that returns NotImplemented, try right arg's __rop__ That's simple to explain and usually works. But w

[issue32892] Remove specific constant AST types in favor of ast.Constant

Guido van Rossum added the comment: I don't feel confident reviewing the code, but I'm okay with the change. Can you describe what usages of the old API will continue to work, and what part will break? (It would seem that code that creates a tree using e.g. Num(42) will still work

[issue34762] Change contextvars C API to use PyObject

Guido van Rossum added the comment: Let’s change it ASAP. It’s still up to Ned whether to hold up 3.7.1, if he won’t it should go into 3.7.2. On Fri, Sep 21, 2018 at 8:28 AM STINNER Victor wrote: > > STINNER Victor added the comment: > > IMHO it's not too late to change th

[issue22490] Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs fragile

Guido van Rossum added the comment: I was pointed here after we found some erroneous behavior. We have a script run by the system python that invokes a specific venv's python3 with a -m flag requesting a module that is installed (only) in that venv. A user complained that this failed,

[issue32117] Tuple unpacking in return and yield statements

Guido van Rossum added the comment: New changeset fd97d1f1af910a6222ea12aec42c456b64f9aee4 by Guido van Rossum (David Cuthbert) in branch 'master': bpo-32117: Allow tuple unpacking in return and yield statements (gh-4509) https://github.com/python/cpyt

[issue32117] Tuple unpacking in return and yield statements

Guido van Rossum added the comment: Fixed by https://github.com/python/cpython/pull/4509. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue22490] Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs fragile

Guido van Rossum added the comment: Jason if you could test this we would be grateful! Ronald what do you think of marking this as backportable to 3.7, 3.6 and 3.5? -- ___ Python tracker <https://bugs.python.org/issue22

[issue22490] Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs fragile

Guido van Rossum added the comment: I would love to know how to repro the original bug so I can demonstrate this actually fixes it. Here's what I think should be the repro: /Library/Frameworks/Python.framework/Versions/3.8/bin/python3 -c 'import subprocess; p = subprocess.Pop

[issue22490] Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs fragile

Guido van Rossum added the comment: Thanks, I have confirmed that this reproduces our issue and that your PR fixes it. I guess at this point we need someone to test with Brew. -- ___ Python tracker <https://bugs.python.org/issue22

[issue34683] Caret positioned wrong for SyntaxError reported by ast.c

Guido van Rossum added the comment: Fixed by gh-9338. Thanks Ammar! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue34683] Caret positioned wrong for SyntaxError reported by ast.c

Guido van Rossum added the comment: Hm, should this be backported? I think it's safest not to. -- ___ Python tracker <https://bugs.python.org/is

[issue34683] Caret positioned wrong for SyntaxError reported by ast.c

Guido van Rossum added the comment: New changeset 025eb98dc0c1dc27404df6c544fc2944e0fa9f3a by Guido van Rossum (Ammar Askar) in branch 'master': bpo-34683: Make SyntaxError column offsets consistently 1-indexed (gh-9338) https://github.com/python/cpyt

[issue34815] Change Py_Ellipse __str__ behavior.

Guido van Rossum added the comment: I'm against this. The str() and repr() of Ellipsis are 'Ellipsis' for a reason: to remind the user that this is "just" an object, not a piece of special syntax. -- ___ Python tracker

[issue21919] Changing cls.__bases__ must ensure proper metaclass inheritance

Guido van Rossum added the comment: As long as you can't crash CPython with this, this is the responsibility of the code that assigns to __bases__. If they don't take care, the program's behavior is undefined. -- ___ Python

[issue34844] logging.Formatter enhancement - Checking on style and fmt fields

Guido van Rossum added the comment: Moving to Python 3.8 because this is a feature proposal. Adding Vinay to nosy list because this is about logging. -- nosy: +vinay.sajip versions: +Python 3.8 -Python 3.6 ___ Python tracker <ht

[issue34845] allow exprlist as the iterators of comprehensions to be consistent with for statements

Guido van Rossum added the comment: This is intentional. We don't want people accidentally writing e.g. [i for i in range(10), j for j in range(10)] -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python t

[issue34854] Crash in string annotations in lambda with keyword-only argument without default value

Guido van Rossum added the comment: Should go to @ambv. On Sun, Sep 30, 2018 at 9:29 AM Serhiy Storchaka wrote: > > Change by Serhiy Storchaka : > > > -- > keywords: +patch > pull_requests: +9037 > stage: -> patch review > > ___

[issue34850] Emit a syntax warning for "is" with a literal

Guido van Rossum added the comment: Yet, Greg’s point is that this only works if the developer tests their code with the new Python version. I’m not sure that his proposal is better though. I think static checkers are the better remedy. On Sun, Sep 30, 2018 at 10:02 AM Serhiy Storchaka wrote

[issue34856] Make the repr of lambda containing the signature and body expression.

Guido van Rossum added the comment: OTOH the current repr is bounded. Some people write very long lambdas. On Sun, Sep 30, 2018 at 11:31 AM Serhiy Storchaka wrote: > > Change by Serhiy Storchaka : > > > -- > keywords: +patch > pull_requests: +9039 >

[issue34850] Emit a syntax warning for "is" with a literal

Guido van Rossum added the comment: Consider moving the chaos discussion to a new issue. On Mon, Oct 1, 2018 at 6:33 AM Steven D'Aprano wrote: > > Steven D'Aprano added the comment: > > On Sun, Sep 30, 2018 at 10:24:41PM +, Nathaniel Smith wrote: > > Would

[issue34538] Remove encouragement to author a base class for all Exception subclasses in a module

Guido van Rossum added the comment: I think as a general recommendation it is not such a good idea that we should specifically mention it. (Is it in PEP 8 too? If so it should be removed there too.) It's a pattern that is sometimes helpful, sometimes not. I don't think that peop

[issue34882] f(a=1, *args) should be a SyntaxError

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue34882> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34498] Python 3.7 breaks on singledispatch_function.register(pseudo_type), which Python 3.6 accepted

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue34498> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34822] Simplify AST for slices

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue34822> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34856] Make the repr of lambda contain signature and body expression.

Guido van Rossum added the comment: However, this is a compatibility liability. People routinely use various formatting options to truncate long strings, since experience shows those are common. But few people expect the repr() of a function/lambda object to be unwieldy

[issue34856] Make the repr of lambda contain signature and body expression.

Guido van Rossum added the comment: OK, if it gets truncated beyond a reasonable length I remove my objection. -- ___ Python tracker <https://bugs.python.org/issue34

[issue34939] Possibly spurious SyntaxError: annotated name can't be global

Guido van Rossum added the comment: I agree with Ivan. -- ___ Python tracker <https://bugs.python.org/issue34939> ___ ___ Python-bugs-list mailing list Unsub

[issue34844] logging.Formatter enhancement - Checking on style and fmt fields

Guido van Rossum added the comment: W00t! Congrats Luna and thanks for your contribution. Thanks Vinay for the prompt reviews! -- ___ Python tracker <https://bugs.python.org/issue34

[issue29341] Missing accepting path-like object in docstrings of os module functions

Change by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/issue29341> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32892] Remove specific constant AST types in favor of ast.Constant

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue32892> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9731] Add ABCMeta.has_methods and tests that use it

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue9731> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35169] Improve error messages for assignment

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue35169> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34805] Explicitly specify `MyClass.__subclasses__()` returns classes in definition order

Guido van Rossum added the comment: Since this is how it works since 3.6, I think it's reasonable to make this part of the spec. For dictionary order we waited a release between implementing it that way and making it part of the spec; effectively we've already waited two release

[issue34805] Explicitly specify `MyClass.__subclasses__()` returns classes in definition order

Guido van Rossum added the comment: Thanks for the long post! Clearly there is more here than the eye can easily see. Nevertheless, I feel that, *in this case*, it's not likely that such a re-implementation will ever happen, so I think it is okay to constrain the future so we can guar

[issue34805] Explicitly specify `MyClass.__subclasses__()` returns classes in definition order

Guido van Rossum added the comment: Josh, I have to ask -- do you have plans to rewrite the __subclasses__ implementation? Because at this point I don't really feel like arguing over the OP's use case. It looks like you have a strong objection over the requested feature th

[issue34805] Explicitly specify `MyClass.__subclasses__()` returns classes in definition order

Guido van Rossum added the comment: OK, I don't have time to keep arguing, and I doubt any other core devs care. We should probably just close it as Won't Fix, since it's not important enough to keep deliberating. Luna, I recommend that you pick

[issue35190] collections.abc.Sequence cannot be used to test whether a class provides a particular interface

Guido van Rossum added the comment: Yeah, the docs need to be clarified. -- ___ Python tracker <https://bugs.python.org/issue35190> ___ ___ Python-bugs-list m

[issue35190] collections.abc.Sequence cannot be used to test whether a class provides a particular interface

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue35190> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33878] Doc: Assignment statement to tuple or list: case missing.

Guido van Rossum added the comment: I would like to see this fixed. On Fri, Nov 9, 2018 at 4:27 AM Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > > I think that the fact that `(a) = 42` is accepted is rather an > implementation detail, and the consequence

[issue35202] Remove unused imports in standard library

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue35202> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35207] Disallow expressions like (a) = 42

Guido van Rossum added the comment: I could have sworn Benjamin showed a fix for this during the core-dev sprint in Seattle... -- ___ Python tracker <https://bugs.python.org/issue35

[issue35207] Disallow expressions like (a) = 42

Guido van Rossum added the comment: Hm, I was thinking of https://github.com/python/cpython/pull/9212/, but that's about keyword arg (where the interpreter incorrectly allowed f((kw)=expr). But on thinking about it more I believe we should allow (a) = (b), so there is no code change req

[issue35207] Disallow expressions like (a) = 42

Guido van Rossum added the comment: Let's close this already. It won't happen. Sorry for the noise. -- ___ Python tracker <https://bugs.python.o

[issue34995] functools.cached_property does not maintain the wrapped method's __isabstractmethod__

Guido van Rossum added the comment: This is runtime behavior, mypy doesn't care either way. It triggers on the presence of the decorator, not on what attributes it sets at runtime on the object. -- ___ Python tracker <https://bugs.py

[issue34995] functools.cached_property does not maintain the wrapped method's __isabstractmethod__

Guido van Rossum added the comment: In mypy there would be no difference between a cached property and a normal one -- the type is the same either way. Caching is the quintessential runtime behavior -- it shouldn't matter for semantics, only for performance. (True, sometimes there are

[issue25988] collections.abc.Indexable

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue25988> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17936] O(n**2) behaviour when adding/removing classes

Guido van Rossum added the comment: I can't think of a use for the order of __subclasses__ so no objection here. — Sent from Mailbox for iPad On Sat, May 25, 2013 at 6:16 AM, Antoine Pitrou wrote: > Antoine Pitrou added the comment: > Note that making tp_subclasses a dic

[issue17947] Code, test, and doc review for PEP-0435 Enum

Guido van Rossum added the comment: Eli, what's wrong with having a backdoor? Python is literally *full* of backdoors. I have a feeling that somehow you are trying to build an Enum class that is unpythonic in its desire to enforce some kind of "ideal enum

[issue18111] Add a default argument to min & max

Guido van Rossum added the comment: +1 -- ___ Python tracker <http://bugs.python.org/issue18111> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18111] Add a default argument to min & max

Changes by Guido van Rossum : -- assignee: gvanrossum -> ___ Python tracker <http://bugs.python.org/issue18111> ___ ___ Python-bugs-list mailing list Unsubscri

[issue18264] enum.IntEnum is not compatible with JSON serialisation

Guido van Rossum added the comment: The proposal to change json from using repr() to str() has unknown dangers. I don't want the str() of IntEnum to return just the decimal string (e.g. "42"), since that breaks half of the usefulness of using the enum in the first place -- pe

[issue18264] enum.IntEnum is not compatible with JSON serialisation

Guido van Rossum added the comment: Modifying json to use str(int(value)) (if it detects isinstance(value, int)) is fine with me too. -- ___ Python tracker <http://bugs.python.org/issue18

[issue18264] enum.IntEnum is not compatible with JSON serialisation

Guido van Rossum added the comment: And similar for floats, really. -- ___ Python tracker <http://bugs.python.org/issue18264> ___ ___ Python-bugs-list mailin

[issue18264] enum.IntEnum is not compatible with JSON serialisation

Guido van Rossum added the comment: Hm. Then I prefer just calling the appropriate builtin, e.g. int(). --Guido van Rossum (sent from Android phone) On Jun 21, 2013 6:08 PM, "Nick Coghlan" wrote: > > Nick Coghlan added the comment: > > Can I vote for something lik

[issue18264] enum.IntEnum is not compatible with JSON serialisation

Guido van Rossum added the comment: Change json to call int() first. --Guido van Rossum (sent from Android phone) On Jun 21, 2013 7:45 PM, "Eli Bendersky" wrote: > > Eli Bendersky added the comment: > > On Fri, Jun 21, 2013 at 6:59 PM, Barry A. Warsaw >wrote: > &

[issue18264] enum.IntEnum is not compatible with JSON serialisation

Guido van Rossum added the comment: Yes for float() -- but for str() it would seem redundant? (Or what's the context?) On Fri, Jun 21, 2013 at 8:23 PM, Ethan Furman wrote: > > Ethan Furman added the comment: > > On 06/21/2013 07:49 PM, Guido van Rossum wrote: >> Eli Bend

[issue18244] singledispatch: When virtual-inheriting ABCs at distinct points in MRO, composed MRO is dependent on haystack ordering

Guido van Rossum added the comment: Wow. This is heady stuff. I can't say I totally get every detail, so I'll just pick on some things you wrote. In particular, I'm not sure I agree that there should be a conflict when there are two applicable base classes with a different dis

[issue18244] singledispatch: When virtual-inheriting ABCs at distinct points in MRO, composed MRO is dependent on haystack ordering

Guido van Rossum added the comment: Hm. I interpret "explicit is better than implicit" very differently. I see a strict priority ordering from better to worse, in cases that would otherwise be ambiguous: 1. explicit base class (ABC or otherwise) 2. ABC explicitly register

[issue18244] singledispatch: When virtual-inheriting ABCs at distinct points in MRO, composed MRO is dependent on haystack ordering

Guido van Rossum added the comment: > Looks like the priority ordering you mention is not yet documented > anywhere. Because up till now it has not been needed -- all you can do with ABCs is use isinstance/issubclass. > It definitely makes sense but I'd like to take a step back

[issue15767] add ModuleNotFoundError

Guido van Rossum added the comment: Hey Brett, Sorry for reopening this issue. I am confused by the spec for ModuleNotFoundError. Look at this (in a pretty recent repo): $ ./python.exe Python 3.4.0a0 (default:8f22e03f5f07, Jun 27 2013, 08:49:16) [GCC 4.2.1 Compatible Apple Clang 4.0 ((tags

[issue18244] singledispatch: When virtual-inheriting ABCs at distinct points in MRO, composed MRO is dependent on haystack ordering

Guido van Rossum added the comment: Ok, let's do it. I just sent you a review of your latest code (admitting I don't actually follow the logic in full detail, so I'm mostly harping on tests and comments...). Regarding the PEP: feel free to update this. Clearly nobody read it

<    33   34   35   36   37   38   39   40   41   42   >