[issue38119] resource tracker destroys shared memory segments when other processes should still have valid access

2021-04-04 Thread Steve Newcomb
Steve Newcomb added the comment: Sometimes a leak is exactly what's wanted, i.e. a standing block of shared memory that allows sharing processes come and go ad libitum. I mention this because I haven't seen anyone mention it explicitly. While turicas's monkeypatch covers

[issue43704] ShareableList() raises TypeError when passing "name" keyword

2021-04-04 Thread Steve Newcomb
Steve Newcomb added the comment: The documentation, which needs some improvement, I think. I'll suggest some improvements when I understand things a little better. For the record, it turned out that SharedMemoryManager was irrelevant, as were sockets. That makes sense since memory

[issue43704] ShareableList() raises TypeError when passing "name" keyword

2021-04-02 Thread Steve Newcomb
Steve Newcomb added the comment: And again with 3.8.8, with the same result. I also tried just using the same shared memory manager again within the same process, just as shown in the documentation. Same result: TypeError: ShareableList() got an unexpected keyword argument 'name

[issue43704] ShareableList() raises TypeError when passing "name" keyword

2021-04-02 Thread Steve Newcomb
Steve Newcomb added the comment: I just tried the same thing on Python-3.10.0a6. Same behavior. -- ___ Python tracker <https://bugs.python.org/issue43

[issue43704] ShareableList() raises TypeError when passing "name" keyword

2021-04-02 Thread Steve Newcomb
New submission from Steve Newcomb : This is especially weird because the Python source code says: class ShareableList: [...] def __init__(self, sequence=None, *, name=None): -- components: Library (Lib) files: shareableListBug.txt messages: 390080 nosy: steve.newcomb priority

[issue35496] left-to-right violation in match order

2018-12-16 Thread Steve Newcomb
Steve Newcomb added the comment: I'm very grateful for your time and attention, and sorry to have distracted you. You're correct when you say: Steven D'Aprano: ...the rightmost alternative matches from position 1 of the text, while the leftmost alternative doesn't ma

[issue35496] left-to-right violation in match order

2018-12-14 Thread Steve Newcomb
New submission from Steve Newcomb : Documentation for the re module insists that matches are made left-to-right within the alternatives delimited by an "or* | group. I seem to have found a case where the rightmost alternative is matched unless it (and only it) is commented out.

[issue28490] inappropriate OS.Error "Invalid cross-device link"

2016-10-20 Thread Steve Newcomb
Steve Newcomb added the comment: Oops. My bad. There was a symlink in one of those paths. The message is valid. -- resolution: -> not a bug status: open -> closed ___ Python tracker <http://bugs.python.org/i

[issue28490] inappropriate OS.Error "Invalid cross-device link"

2016-10-20 Thread Steve Newcomb
New submission from Steve Newcomb: os.rename() raises OSError with a misleading message saying "cross-device" when no cross-device activity is involved. Here, running on Ubuntu 16.04.1 using and ext4 filesystem, both filepaths are in the same filesystem, and the error is eviden

[issue11632] difflib.unified_diff loses context

2016-10-18 Thread Steve Newcomb
Steve Newcomb added the comment: Context reporting is still buggy in Python 3.5.2: >>> [ x for x in difflib.unified_diff( "'on'\n", "'on'\n\n\n")] ['--- \n', '+++ \n', '@@ -3,3 +3,5 @@\n', ' n', " 

[issue27898] regexp performance degradation between 2.7.6 and 2.7.12

2016-09-02 Thread Steve Newcomb
Steve Newcomb added the comment: On 08/30/2016 12:46 PM, Raymond Hettinger wrote: > Raymond Hettinger added the comment: > > It would be helpful if you ... make a small set of regular expressions that > demonstrate the performance regression. > Done. Attachments: test.py : Code

[issue27898] regexp performance degradation between 2.7.6 and 2.7.12

2016-09-01 Thread Steve Newcomb
Steve Newcomb added the comment: On 09/01/2016 05:01 PM, Steve Newcomb wrote: > >> The outputs show that 2.7.12's re.sub() takes 1.2 times as long as >> 2.7.6's. It's a significant difference, but... >> >> ...it was not the dramatic degradation I

[issue27898] regexp performance degradation between 2.7.6 and 2.7.12

2016-09-01 Thread Steve Newcomb
Steve Newcomb added the comment: Oops. The correct url is sftp://coolheads.com/files/py-re-perform-276v2712/ On 09/01/2016 04:52 PM, Steve Newcomb wrote: > On 08/30/2016 12:46 PM, Raymond Hettinger wrote: >> Raymond Hettinger added the comment: >> >> It would be helpful if

[issue27898] regexp performance degradation between 2.7.6 and 2.7.12

2016-08-30 Thread Steve Newcomb
Steve Newcomb added the comment: On 08/30/2016 01:24 PM, Serhiy Storchaka wrote: > Serhiy Storchaka added the comment: > > According to your profile results all re functions are 2.5-4 times faster > under 2.7.12 than under 2.7.6. May be I misinterpret it? I can't explain the

[issue27898] regexp performance degradation between 2.7.6 and 2.7.12

2016-08-30 Thread Steve Newcomb
Steve Newcomb added the comment: On 08/30/2016 12:46 PM, Raymond Hettinger wrote: > Raymond Hettinger added the comment: > > It would be helpful if you could run "hg bisect" with your set-up to isolate > the change that causes the problem. I don't think I understand

[issue27898] regexp performance degradation between 2.7.6 and 2.7.12

2016-08-30 Thread Steve Newcomb
New submission from Steve Newcomb: Our most regular-expression-processing-intensive Python 2.7 code takes 2.5x more execution time in 2.7.12 than it did in 2.7.6. I discovered this after upgrading from Ubuntu 14.04 to Ubuntu 16.04. Basically this code runs thousands of compiled regular

[issue15956] backreference to named group does not work

2012-09-18 Thread Steve Newcomb
Steve Newcomb added the comment: > I preferred the previous example "" because it's not obvious what > \042\047 is. Yeah, but the example I wrote has an in-pattern backreference and a real reason to use one. In the attached patch, I have changed [\042\047] to [\&#

[issue15956] backreference to named group does not work

2012-09-18 Thread Steve Newcomb
Steve Newcomb added the comment: > But this way exists: (?P=startquote) is what you want. I know how I missed it: I searched for "backref" in the documentation. I did not find it in the discussion of the pattern language, because that word does not appear where contribution

[issue15956] backreference to named group does not work

2012-09-17 Thread Steve Newcomb
Steve Newcomb added the comment: I have re-read the documentation on re.sub(). Even now, now that I understand that the \g syntax applies to the repl argument only, I cannot see how the documentation can be understood that way. The paragraph in which the explanation of the \g syntax appears

[issue15956] backreference to named group does not work

2012-09-17 Thread Steve Newcomb
New submission from Steve Newcomb: The '\\g' in the below does not work: >>> repr( re.compile( '\\<\\!ENTITY[ \\011\\012\\015]+\\%[ >>> \\011\\012\\015]*(?P[A-Za-z][A-Za-z0-9\\.\\-\\_\\:]*)[ >>> \\011\\012\\015]*(?P[\\042\\047])(?P.+?)\\g[ >>