[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Paul Moore p.f.moore at gmail.com
Mon Mar 10 22:54:12 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 ]
On 10 March 2014 19:42, Serhiy Storchaka <storchaka at gmail.com> wrote:
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".
I understand that - my concern is that people reading such comments out of context might not realise this ("after all, that was what Python 3000 meant, then you went and implemented it"). Paul
- 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 ]