[issue36777] unittest discover throws TypeError on empty packages

Change by Gus Goulart : -- keywords: +patch pull_requests: +13169 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36777> ___ ___ Py

[issue36777] unittest discover throws TypeError on empty packages

Gus Goulart added the comment: Confirming that the issue seems to have been introduced on 3.7. Working on this at the PyCon US 2019 sprints. -- nosy: +gus.goulart ___ Python tracker <https://bugs.python.org/issue36

[issue33930] Segfault with deep recursion into object().__dir__

Gus Goulart added the comment: After a couple of rounds, this is the benchmark result I got for the attached patch. It seems to be a simple, non-performance degrading fix. python -m perf compare_to origin.json patch.json -G --min-speed=2 Slower (1): - sqlalchemy_declarative: 213 ms +- 4 ms

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Gus Goulart added the comment: @vstinner, on Debian 9 I can see the problem as well but wasn't able to debug with the level of details you did. Could you please share the process you followed? What I found was: ./python -X dev test_lock_sigsegv.py Parent r_q: , , Fatal Python error

[issue33930] Segfault with deep recursion into object().__dir__

Gus Goulart added the comment: Sorry, I forgot to include the trashcan API. I'll double check and update the issue. -- ___ Python tracker <https://bugs.python.org/issue33

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Gus Goulart added the comment: I've tested on Fedora 29 server and also failed to reproduce the error. -- Added file: https://bugs.python.org/file47931/testing_on_fedora.png ___ Python tracker <https://bugs.python.org/issue33

[issue33930] Segfault with deep recursion into object().__dir__

Change by Gus Goulart : -- nosy: +taleinat ___ Python tracker <https://bugs.python.org/issue33930> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33930] Segfault with deep recursion into object().__dir__

Gus Goulart added the comment: ronaldoussoren, I have tested (Debian 9) substituting "_PyObject_GC_UNTRACK(m);" to "PyObject_GC_UnTrack(m);", and although the tests pass, I'm can still see the segfault error. diff --git a/Objects/methodobject.c b/Objects/methodobjec

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Change by Gus Goulart : -- nosy: +taleinat ___ Python tracker <https://bugs.python.org/issue33196> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Gus Goulart added the comment: I couldn't reproduce the error on Debian 9 nor OSX, although I tried tweaking the test script a little bit to force the error. Arcadiy, did you tried reproducing the same issue in a different platform? Did someone report something similar in recent issues

[issue32485] Multiprocessing dict sharing between forked processes

Gus Goulart added the comment: This is probably a bug that was fixed sometime in Python 3x. Testing on 3.7.1, Python gracefully errors out: ``` ➜ cpython git:(bpo-32485) ✗ python issue_32485.py Same manager, same mux Starting test_sameProcessSameThread Traceback (most recent call last

[issue33678] selector_events.BaseSelectorEventLoop.sock_connect should preserve socket type

Gus Goulart added the comment: This error seems to come from base_events.py, lines 142-145, and since it's an OS specific limitation, I can't see Sebastien's suggestion as a feasible solution. Maybe we could come up with something along the lines of the following patch. What do you think

[issue27741] datetime.datetime.strptime functionality description incorrect

Change by Gus Goulart : -- keywords: +patch pull_requests: +9335 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue27741> ___ ___ Py

[issue27741] datetime.datetime.strptime functionality description incorrect

Gus Goulart added the comment: Thanks, Tal. I will open up a PR for it. -- ___ Python tracker <https://bugs.python.org/issue27741> ___ ___ Python-bugs-list m

[issue27741] datetime.datetime.strptime functionality description incorrect

Gus Goulart added the comment: As far as I can see, every time something changes on datetime.strptime(), it will invalidate that section of the documentation. On the other hand, I believe the comparison with datetime(*(time.strptime(date_string, format)[0:6])" is interesting and val

[issue34187] Issues with lazy fd support in _WindowsConsoleIO fileno() and close()

Change by Gus Goulart : -- keywords: +patch pull_requests: +9275 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue27741] datetime.datetime.strptime functionality description incorrect

Change by Gus Goulart : -- nosy: +taleinat ___ Python tracker <https://bugs.python.org/issue27741> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27741] datetime.datetime.strptime functionality description incorrect

Gus Goulart added the comment: It is true that time.srtptime() does not return microseconds, but as the documentation suggests, it will return the microseconds after you wrap it up with datetime(). I have attached a walkthrough of how I see that section of the docs. Please let me know

[issue34203] documentation: recommend Python 3 over 2 in faq

Gus Goulart added the comment: Thanks for pointing that out. If you don't mind, I have created a PR to address your requests. -- nosy: +gus, taleinat ___ Python tracker <https://bugs.python.org/issue34

[issue34203] documentation: recommend Python 3 over 2 in faq

Change by Gus Goulart : -- keywords: +patch pull_requests: +9180 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue34187] Issues with lazy fd support in _WindowsConsoleIO fileno() and close()

Gus Goulart added the comment: Hi everyone, I would like to let you know that I'm starting working on this one. Thanks! -- nosy: +Gus ___ Python tracker <https://bugs.python.org/issue34