[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Serhiy Storchaka storchaka at gmail.com
Mon Mar 10 20:42:54 CET 2014
- Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
10.03.14 20:50, Paul Moore написав(ла):
I have seen a number of postings recently pointing to things as "not until Python 4000" or "not until Python 4.0" (yours was not one that I noticed, actually, this is a more general point).
This is just an euphemism for "not in observable future".
- Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]