-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Apr 08, 2013, at 05:08 PM, Tres Seaver wrote:
>FWIW, the effort of porting the "modern" bits of the Zope ecosystem (the >ones I still use in Pyramid apps today, meaning the component >architecture, the ZODB, and a few others) soaked up basically all of my >FLOSS time between the two Santa Clara PyCons. > >To be fair, some of that effort went into improving test coverage, docs, >etc., to ensure that the apps running against the ported librarties >wouldn't break, even on Python2: but is was *not* a trivial effort. I've ported a ton of stuff, most of it not written by me. The actual job of porting (not counting convincing your manager to let you do it) will either be easy and quick or painful and difficult <wink>. It's often hard to know before you start. It almost always comes down to bytes vs. strings, IME. Sometimes, the code you're porting has a clear model and you just have to understand it, and then the porting goes fairly smoothly. Often, the model isn't clear or there *is* no distinction, in which case your life will suck. It's important to realize that everyone doing porting work now is also making Python 3 better by helping to find the pain points in the language and stdlib. The u-prefix is a perfect example of this. .format() on bytes (issue3982) and some of the discussions around issue17445 are two examples where we're at least identifying additional pain, if not yet fixing it. Python 3.3 is easier to port to than 3.2 is. I hope that we'll be able to take all of our experiences and funnel that into 3.4 to make it a better porting target still. Then, even though people will still be using Python 2 when Orlijn is BDFL, we'll at least be making progress. We also want to make 3.4 and future Python 3 releases so compelling that starting new projects in Python 3 will be a no-brainer, and we want to make sure that the batteries, both in the stdlib and 3rd party are up to the task. Eventually Python 2 programmers will be like today's COBOL programmers (which is good for future employment prospects :), but there's more Python 3 code out there waiting to be written than there is existing Python 2 code today. :) Don't worry about what you *can't* port! - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRYz8jAAoJEBJutWOnSwa/lsQP/jyIYBzfl9eDXw81Ar4t+Uls 7JOYfQqQXhMXL2f1XLHivCplhso0YBZn2ZepXJ9kLJ4SnO7bPZbo+esD99IoAlhG QXjlvUnrSsc9mQG16HeuQLHjRmiZPg/mT+ACPuv3/ixxZggaKga7Jdcr2Xpo4KIS 89WzG2MWYhVGr3o28AAgSkSN/4fbmXRzjwmox0QjyhPdM6CWbTLO5KkF1cOLIXi/ UyYmlZAwSqVxR6cVRsGVwLStUy417UwZnc0h71IJxgRwgXOZDXzVKPvy/JqbVsK7 451aWB/mTkiaKkp+Qi0ebjZLLmSyEITS8DOurZKIy4Qfppyqy+patwazsY113zAg wdexiFfFc2W4zLFflxTScqULFJulYyL7KzSsQBHPcou1G5nDUVXBXoM+AC71EBtd TE+tyAhZWE38/mfDtOBCJCkJzevzJWF4tpGVgm1Gd5hSU7M8Yb2NQcZLYY0UxzZK weDItJUYTSYEQh6j9nBlZGaX9v62SnXPlZaV2s9/bbVFsHekwYQcEAFlpGUqeUxi KFFzS1GUl8IE8ZcHJDVW6U3YXzBSUKdSBa55IHw5hD+I730WAj8wq8aH7yFhyyzv jyFRdhtEFhapnA2zpxogFGVLPRjl9iOphfVnUR6wNuh7q+226GsqHyaMbkWBM9Cb sg39ITeWH6C0jMMxiGfx =ZAcF -----END PGP SIGNATURE----- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com