[lxml-dev] first lessons learned while porting lxml to Py3

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Behnel wrote:
> Hi,
> 
> Martijn Faassen wrote:
>> I'm glad to hear that you'll try being more clear with how unicode works 
>> for the Python 2.x version of lxml too. I think this is similar to the 
>> way the migration path enables this for plain Python code in Python 2.6.
> 
> There will be little changes when running in Py2. It will still accept byte
> strings at the API level and return them for plain ASCII values. This only
> changes under Py3, where you will always get a unicode string back for .tag,
> .text, etc.
> 
> I'm not even planning to block passing byte strings as tag name, although that
> will become really rare for Python code running in Py3.
> 
> 
>> I do hope that lxml for Python 2.x can be maintained and extended for 
>> the forseeable future though; I'm sitting on a vast mountain of 
>> codebases that aren't going to Python 3.x in a hurry.
> 
> There will only be a single code base. We ported the code that Cython
> generates in a way that makes it compile from Py2.3 to Py3.0 without changes,
> and I'm planning to continue the support for 2.3 as long as possible.

Thank you!  /me heaves a huge sigh of relief.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIQYyv+gerLs4ltQ4RAoaYAJ9tfnofSKDkniA2KV7mPa4AUg7UhACfQoIy
5zcGRMv37Fu4ZWIEmC8E5v0=
=hp1x
-----END PGP SIGNATURE-----