If nothing else, this would make our Travis builds schedule 2X fewer jobs.
Concretely, I think this would involve dropping the python 2.7 jobs from .travis.yml and adding a statement to the readme saying that Python 2.7 will probably work but isn't officially tested anymore, and that we won't fix Python 2.7 bugs after 2019-07-04 (or 6 months from whatever date we choose to drop support).
Nicholas Carlini
unread,
Jan 4, 2019, 3:43:46 PM1/4/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Link
Report message as abuse
Sign in to report message as abuse
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ian Goodfellow, cleverhans dev
Yes. Python3 is is 10 years old now. The world should move on.