[issue31169] Unknown-source assertion failure in multiprocessing/managers.py

2017-08-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Now fixed in git master thanks to drallensmith. -- resolution: -> fixed stage: -> resolved status: open -> closed versions: -Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker

[issue31169] Unknown-source assertion failure in multiprocessing/managers.py

2017-08-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: New changeset 48d9823a0ebde4dfab8bc154bb6df462fb2ee403 by Antoine Pitrou (Allen W. Smith, Ph.D) in branch 'master': bpo-5001, bpo-31169: Fix two uninformative asserts in multiprocessing/managers.py (#3078) https://github.com/python/cpython/commit/48d9823a0ebde

[issue31169] Unknown-source assertion failure in multiprocessing/managers.py

2017-08-12 Thread drallensmith
drallensmith added the comment: Pull request equivalent for the patch submitted. This will not, of course, fix this particular bug, but it should help others with debugging such errors. -- ___ Python tracker _

[issue31169] Unknown-source assertion failure in multiprocessing/managers.py

2017-08-12 Thread drallensmith
Changes by drallensmith : -- pull_requests: +3118 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue31169] Unknown-source assertion failure in multiprocessing/managers.py

2017-08-10 Thread drallensmith
drallensmith added the comment: I've updated the title to be more accurate. On second thought, putting in a pdb.set_trace() would require that I know where the assertion failure is taking place... sigh. BTW, is there some way to edit earlier messages? I am used to github in that regard... ---