Brett Cannon added the comment:

I have not looked at your patch, tzickel, but I just wanted to let you know a 
lack of reply just means lack of time on the part of the core developers. We 
are all volunteers and essentially don't get paid to spend our time to work on 
Python. Add in the fact that this is an odd edge case issue on Python 2.7 and 
that lowers the priority for someone to get to it when there are more pressing 
issues related to the new 3.5.0 release.

Hopefully someone who has a good understanding of the low-level C details you 
are talking about in your patch will be able to make a good judgment as to 
whether the test case and patch make sense.


Python tracker <>
Python-bugs-list mailing list

Reply via email to