[issue38263] [Windows] multiprocessing: DupHandle.detach() race condition on DuplicateHandle(DUPLICATE_CLOSE_SOURCE)

2021-04-09 Thread Leonardo Rick
Leonardo Rick added the comment: Traceback (most recent call last): File "", line 1, in File "C:\Program Files\Python39\lib\multiprocessing\spawn.py", line 116, in spawn_main exitcode = _main(fd, parent_sentinel) File "C:\Program Files\Python39\lib\multip

[issue42620] documentation on `getsockname()` wrong for AF_INET6

2020-12-11 Thread Rick van Rein
Rick van Rein added the comment: Excellent, thanks. I personally would appreciate if a remark about IPv6 would also be made. -- ___ Python tracker <https://bugs.python.org/issue42

[issue42620] documentation on `getsockname()` wrong for AF_INET6

2020-12-11 Thread Rick van Rein
New submission from Rick van Rein : Shown in the session below is unexpected output of a 4-tuple from an AF_INET6 socket along with documentation that *suggests* to expect a 2-tuple. The phrasing "IP" might have to be toned down to "IPv4" or "AF_INET" t

[issue37296] pdb next vs __next__

2020-09-16 Thread Rick
Rick added the comment: I have no idea what program this was in, it's lost in the depths of time. I can't retain these things for over a year, too old, maybe in my twenties I would have remembered what code this was in but no long

[issue39580] Check for COMMAND_LINE_INSTALL variable in Python_Documentation.pkg

2020-05-20 Thread Rick Heil
Change by Rick Heil : -- keywords: +patch nosy: +rickheil nosy_count: 3.0 -> 4.0 pull_requests: +19551 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20271 ___ Python tracker <https://bugs.python.org/i

[issue39580] Check for COMMAND_LINE_INSTALL variable in Python_Documentation.pkg

2020-05-20 Thread Rick Heil
Rick Heil added the comment: In case folks reading this are not aware, installer(8) sets an environmental variable COMMAND_LINE_INSTALL when an installation is triggered on the command line versus when a user double-clicks a package in the GUI to kick off the install. I've filed the l

[issue39637] Probably incorrect message after failed import

2020-02-15 Thread Rick van Rein
Change by Rick van Rein : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue39637> ___ ___

[issue39637] Probably incorrect message after failed import

2020-02-15 Thread Rick van Rein
Rick van Rein added the comment: Thanks for explaining. It is indeed confusing, even though I'm quite experienced with Python. -- ___ Python tracker <https://bugs.python.org/is

[issue39637] Probably incorrect message after failed import

2020-02-15 Thread Rick van Rein
New submission from Rick van Rein : The following error message surprises me: >>> import os.environ Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'os.environ'; 'os' is not a package Shouldn't that s

[issue37296] pdb next vs __next__

2019-06-15 Thread Rick
New submission from Rick : Don't know how to get version from pdb, Makefile says 2.7 Code runs but when debugging I get an error that an iterator has no next() function. It has got a __next__() function, and it runs, just not under pdb. If I create a spurious next() function, pdb runs

[issue31725] Turtle/tkinter: NameError crashes ipython with "Tcl_AsyncDelete: async handler deleted by the wrong thread"

2018-06-16 Thread Rick J. Pelleg
Rick J. Pelleg added the comment: Thanks! On Sat, Jun 16, 2018, 18:53 Carol Willing wrote: > > Carol Willing added the comment: > > Hi Rick, > > I'm closing this issue as not reproducible. Thanks for filing it and using > Turtle. > > -- > nosy: +w

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

2018-05-11 Thread Rick Teachey
Rick Teachey added the comment: Lending my voice to the suggestion of limiting the class attribute check to `typing.ClassVar` and `ClassVar`. It can always be expanded later if it is needed. -- ___ Python tracker <https://bugs.python.

[issue33453] from __future__ import annotations breaks dataclasses ClassVar and InitVar handling

2018-05-10 Thread Rick Teachey
Rick Teachey added the comment: > Is there any scenario where the following code would be useful... Perhaps if someone, in search of a speedup, were sort of rolling their own lighter-weight equivalent to the typing module (in order to avoid importing the full typing module), but duck ty

[issue33452] add user notification that parent init will not be called in dataclass init method

2018-05-09 Thread Rick Teachey
Rick Teachey added the comment: The init method that comes up for int, str, float, etc is just the object init: assert int.__init__ is object.__init__ Probably the thing to do is grab any init methods that aren't the object.__init__ while stripping out the dataclass-created init me

[issue33453] from __future__ import annotations breaks dataclasses ClassVar handling

2018-05-09 Thread Rick Teachey
Rick Teachey added the comment: Sorry, mean to say it works just fine *without* the import. -- ___ Python tracker <https://bugs.python.org/issue33453> ___ ___

[issue33453] from __future__ import annotations breaks dataclasses ClassVar handling

2018-05-09 Thread Rick Teachey
Rick Teachey added the comment: To be clear: it works just fine with the annotations import. -- ___ Python tracker <https://bugs.python.org/issue33453> ___ ___

[issue33453] from __future__ import annotations breaks dataclasses ClassVar handling

2018-05-09 Thread Rick Teachey
New submission from Rick Teachey : This is broken in 3.7 (both beta 3 and 4): from __future__ import annotations from dataclasses import dataclass from typing import ClassVar, Any @dataclass class C(): class_var: ClassVar[Any] = object() data: str Traceback: Traceback (most recent

[issue33452] add user notification that parent init will not be called in dataclass init method

2018-05-09 Thread Rick Teachey
New submission from Rick Teachey : The dataclasses module is incredibly easy to use. This is a good thing. BUT one downside is it will definitely be utilized by people who don't have a thorough understanding of how it does what it does. Even for me, despite having a very good understandi

[issue33328] pdb error when stepping through generator

2018-04-29 Thread Rick Teachey
Rick Teachey added the comment: Closed as duplicate of issue 13044. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33328] pdb error when stepping through generator

2018-04-21 Thread Rick Teachey
Rick Teachey added the comment: I am on Anaconda 4.5.1 on Windows 10 (Python 3.6.5). I have confirmed that I DO get the error on another machine with the same version installed, so the lack of an error seems specific to my current machine. I do not know what could be causing this; it is very

[issue33328] pdb error when stepping through generator

2018-04-21 Thread Rick Teachey
Change by Rick Teachey : -- components: +Library (Lib) type: -> behavior ___ Python tracker <https://bugs.python.org/issue33328> ___ ___ Python-bugs-list mai

[issue33328] pdb error when stepping through generator

2018-04-21 Thread Rick Teachey
Rick Teachey added the comment: The interactive session result is below: GeneratorExit Exception ignored in: Traceback (most recent call last): File "C:\Users\ricky\AppData\Local\Programs\Python\Python37\lib\types.py", line 27, in _ag File "C:\Users\ricky\AppData\Local\

[issue33328] pdb error when stepping through generator

2018-04-21 Thread Rick Teachey
New submission from Rick Teachey : Hello: The attached python file runs a pdb interactive session for a generator. It produces an error in Python 3.7 Beta 3, but no error in 3.6. I searched for this issue and there do seem to be things that are related to it already, but I haven&#

[issue33190] problem with ABCMeta.__prepare__ when called after types.new_class

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: Thank you; I gave it a go. Hopefully didn't cause too much additional work for someone. -- ___ Python tracker <https://bugs.python.org/is

[issue33190] problem with ABCMeta.__prepare__ when called after types.new_class

2018-03-30 Thread Rick Teachey
Change by Rick Teachey : -- keywords: +patch pull_requests: +6033 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33190> ___ ___ Py

[issue33188] dataclass MRO entry resolution for type variable metaclasses: TypeError

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: I'll also say: one of the biggest reasons I was excited to read the `dataclasses` PEP was because I thought "AWESOME! Now I can delete all of the stupid boilerplate __init__ and __repr__ methods for those `typing.Sequences`, `typing.Mapping

[issue33188] dataclass MRO entry resolution for type variable metaclasses: TypeError

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: > passing keyword arguments to metaclass will be much more rare for dataclasses > than passing a ready namespace The impetus of my running into these issues was assuming that things like `Generic[MyTypeVar]` would "just work" with `make_d

[issue33188] dataclass MRO entry resolution for type variable metaclasses: TypeError

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: Eric: see also Ivan's comment on Issue 33190, which will factor into the solution to this I think. It seems you can't just pass the `namespace` to the `kwds` argument (as I have done in my solu

[issue33190] problem with ABCMeta.__prepare__ when called after types.new_class

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: Excellent; thank you very much for the explanation. I have never done a PR on a project this size but I'll give it a try. -- ___ Python tracker <https://bugs.python.org/is

[issue33190] problem with ABCMeta.__prepare__ when called after types.new_class

2018-03-30 Thread Rick Teachey
New submission from Rick Teachey : I am pretty sure this is a bug. If not I apologize. Say I want to dynamically create a new `C` class, with base class `MyABC` (and dynamically assigned abstract method `m`). This works fine if I use `type`, but if I use `new_class`, the keyword argument to

[issue33188] dataclass MRO entry resolution for type variable metaclasses: TypeError

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: Same error on 3.7. Probably getting beyond my knowledge here but from the error message, it seems like the answer is simply that: type('MyChild', (MyParent[int],), {}) ...is just the wrong way to make a new `type` when utilizing type

[issue33188] dataclass MRO entry resolution for type variable metaclasses: TypeError

2018-03-30 Thread Rick Teachey
Rick Teachey added the comment: Sorry: to be clear, the error only occurs when attempting to create the class using `make_dataclass`. -- ___ Python tracker <https://bugs.python.org/issue33

[issue33188] dataclass MRO entry resolution for type variable metaclasses: TypeError

2018-03-30 Thread Rick Teachey
New submission from Rick Teachey : I'm getting the following error at when attempting to create a new `dataclass` with any base class that is supplied a type variable: TypeError: type() doesn't support MRO entry resolution; use types.new_class() In principle, it seems like this

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-26 Thread Rick Teachey
Rick Teachey added the comment: Looks great to me. Thanks! -- ___ Python tracker <https://bugs.python.org/issue33141> ___ ___ Python-bugs-list mailing list Unsub

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-26 Thread Rick Teachey
Rick Teachey added the comment: Yeah and I think lines 2709-2712 of TestDescriptors also needs removed. -- ___ Python tracker <https://bugs.python.org/issue33

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-26 Thread Rick Teachey
Rick Teachey added the comment: Eric, looking at the PR; note that if you do this for the __set_name__ check: if inspect.ismethoddescriptor(self.default): ...an object like the one below will not get its __set_name__ called, even though PEP 487 says it should: class D: def

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-26 Thread Rick Teachey
Rick Teachey added the comment: I suppose one downside of that solution is __set_name__ will be called for every Field whether or not it is need. Probably can't be helped without major complications. -- ___ Python tracker <https://bugs.py

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-26 Thread Rick Teachey
Rick Teachey added the comment: Sounds like a relatively easy solution then. Hopefully it makes the beta 3 so I can use it immediately- thanks! -- ___ Python tracker <https://bugs.python.org/issue33

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-26 Thread Rick Teachey
Rick Teachey added the comment: hmmm... if I check the C.d class attribute it seems to return the descriptor instance object (not a field object) before any C instances have been created. i guess this is just a part of how the dataclass implementation works. i didn't realize there'

[issue33141] descriptor __set_name__ feature broken for dataclass descriptor fields

2018-03-25 Thread Rick Teachey
New submission from Rick Teachey : Summary: The descriptor `__set_name__` functionality (introduced in Python 3.6) does not seem to be working correctly for `dataclass.Field` objects with a default pointing to a descriptor. I have attached a file demonstrating the trouble. Details: If I set

[issue31725] Turtle/tkinter: NameError crashes ipython with "Tcl_AsyncDelete: async handler deleted by the wrong thread"

2017-10-14 Thread Rick J. Pelleg
Rick J. Pelleg added the comment: Just one more issue: since it happened before I found out that the "turtle" package already has the pre-defined short version of commands, such as "fd()", "lt()", etc., the crashed session included four function definitions, for

[issue31725] Turtle/tkinter: NameError crashes ipython with "Tcl_AsyncDelete: async handler deleted by the wrong thread"

2017-10-14 Thread Rick J. Pelleg
Rick J. Pelleg added the comment: Sorry, all reproduction attempts failed, both in plain Python and in iPython. I guess you can close this for now. -- ___ Python tracker <https://bugs.python.org/issue31

[issue31725] Turtle/tkinter: NameError crashes ipython with "Tcl_AsyncDelete: async handler deleted by the wrong thread"

2017-10-08 Thread Rick J. Pelleg
Rick J. Pelleg added the comment: Mmm... right now I cannot reproduce at all, both in iPython and in python. Will continue to try. -- ___ Python tracker <https://bugs.python.org/issue31

[issue31725] Turtle/tkinter: NameError crashes ipython with "Tcl_AsyncDelete: async handler deleted by the wrong thread"

2017-10-08 Thread Rick J. Pelleg
New submission from Rick J. Pelleg : On Windows 10 Education, ran: ipython Python 3.6.3 (v3.6.3:2c5fed8, Oct 3 2017, 17:26:49) [MSC v.1900 32 bit (Intel)] Type 'copyright', 'credits' or 'license' for more information IPython 6.2.1 -- An enhanced Interactive Python.

[issue23532] regex "|" behavior differs from documentation

2015-02-26 Thread Rick Otten
Rick Otten added the comment: Can the documentation be updated to make this more clear? I see now where the clause "As the target string is scanned, ..." is describing what you have listed here. I and a coworker both read the description several times and missed that. I though

[issue23532] regex "|" behavior differs from documentation

2015-02-26 Thread Rick Otten
New submission from Rick Otten: The documentation states that "|" parsing goes from left to right. This doesn't seem to be true when spaces are involved. (or \s). Example: In [40]: mystring Out[40]: 'rwo incorporated' In [41]: re.sub('incorporated

[issue23532] regex "|" behavior differs from documentation

2015-02-26 Thread Rick Otten
Changes by Rick Otten : -- components: Regular Expressions nosy: Rick Otten, ezio.melotti, mrabarnett priority: normal severity: normal status: open title: regex "|" behavior differs from documentation type: behavior versions: Python 2.7

[issue14470] Remove using of w9xopen in subprocess module

2012-04-20 Thread Rick Rune
Rick Rune added the comment: Removed w9xpopen usage in subprocess module via attached patch. -- keywords: +patch nosy: +Rune Added file: http://bugs.python.org/file25296/subprocess_minus_w9xpopen.patch ___ Python tracker <http://bugs.python.

[issue9009] Improve quality of Python/dtoa.c

2011-12-01 Thread Rick Regan
Rick Regan added the comment: > if (!(dig = quorem(b,d))) { > b = multadd(b, 10, 0); /* very unlikely */ > dig = quorem(b,d); > } > > This code is part of the algorithm for strtod. Here b and d are > Bigints, and b / d is

[issue1675951] [gzip] Performance for small reads and fix seek problem

2010-06-16 Thread Rick Harris
Rick Harris added the comment: Are compatibility concerns the main reason this patch has yet to be applied? If so, could we allay those fears by keeping the default seek-y behavior and only introducing the new seek-less style when a 'noseek' flag is passed? -- nosy

[issue8970] Tkinter Litmus Test

2010-06-11 Thread Rick Johnson
Changes by Rick Johnson : -- status: open -> closed ___ Python tracker <http://bugs.python.org/issue8970> ___ ___ Python-bugs-list mailing list Unsubscri

[issue8971] Tkinter Litmus Test

2010-06-11 Thread Rick Johnson
New submission from Rick Johnson : There has been much discussion in the past and recently on c.l.p about how many python programmers *actually* use Tkinter. Recently i have been involved in a lengthy discussion on c.l.p about whether or not we should remove Tkinter, replace Tkinter, or fix

[issue8970] Tkinter Litmus Test

2010-06-11 Thread Rick Johnson
New submission from Rick Johnson : There has been much discussion in the past and recently on c.l.p about how many python programmers *actually* use Tkinter. Recently i have been involved in a lengthy discussion on c.l.p about whether or not we should remove Tkinter, replace Tkinter, or fix

[issue1346874] httplib simply ignores CONTINUE

2008-08-07 Thread Rick Harris
Rick Harris <[EMAIL PROTECTED]> added the comment: I'm implemented the behavior described by Mike above with a patch to 2.6. The patch will raise an ExpectationFailed before sending the body if the server responds with a 417 (Expectation Failed). This patch should only modify b

[issue2651] Strings passed to KeyError do not round trip

2008-04-17 Thread Rick Harris
Rick Harris <[EMAIL PROTECTED]> added the comment: I think it is important to round-trip for at least two reasons: 1) Consistency. Other built-in exceptions behave this way, why should KeyError be any different? Okay, technically 3 UnicodeErrors don't allow just strings to be passed

[issue2651] Strings passed to KeyError do not round trip

2008-04-17 Thread Rick Harris
New submission from Rick Harris <[EMAIL PROTECTED]>: Here is a bug in Python 2.5 which would be nice to fix for Py3k (since we are already breaking compatibility): Take a string: s = "Hello" Create a KeyError exception with that string: e = KeyError(s) Counterintuitiv

[issue2116] weakref copy module interaction

2008-04-03 Thread Rick Harris
Rick Harris <[EMAIL PROTECTED]> added the comment: Sorry about forgetting the -c arg! The patch is intended for python/trunk/Lib/copy.py. It looks like Raymond Hettinger has made a similar-ish change recently to make Ellipsis copyable. __ Tracker &

[issue2116] weakref copy module interaction

2008-02-14 Thread Rick Harris
New submission from Rick Harris: The copy module will not properly copy/deepcopy weakrefs, it will bomb out with __new__ not having enough args. This is a problem b/c it makes deepcopying of objects that make use of Weak(Key|Value)Dictionaries difficult. To replicate: import copy, weakref