➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients martin.panter, python-dev, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-11-21.15:52:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479743541.08.0.374401583515.issue28688@psf.upfronthosting.co.za>
In-reply-to
Content 
I implemented x==y operator for _sre.SRE_Pattern in Python 3.6 and 3.7, it fixed this issue.

For Python 3.5, I removed the warnings.filters test, as we discussed.

@Martin Panter: immortal-filters.patch works because I'm not super excited by the change. Somehow, it looks like a hack... even if I don't see any better solution for Python 3.5.

Since the bug only impacts Python test suite in the practical, is it really worth it to fix it in Python 3.5 which is almost in the "security fix only" stage?


@Martin: It's up to you, I have no strong opinion on your patch.


> I agree there is no need to change Python 2 at this stage.

Ok.
History
Date User Action Args
2016-11-21 15:52:21vstinnersetrecipients: + vstinner, python-dev, martin.panter, serhiy.storchaka, xiang.zhang
2016-11-21 15:52:21vstinnersetmessageid: <1479743541.08.0.374401583515.issue28688@psf.upfronthosting.co.za>
2016-11-21 15:52:21vstinnerlinkissue28688 messages
2016-11-21 15:52:20vstinnercreate