[issue34894] Unexpected error while unpickling lxml.etree.Element object

Marcin Raczyński added the comment: Thanks Serhiy for explanation! I quote your comment in a lxml issue tracker: https://bugs.launchpad.net/lxml/+bug/736708 -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue34894] Unexpected error while unpickling lxml.etree.Element object

Change by Serhiy Storchaka : -- nosy: +scoder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue34894] Unexpected error while unpickling lxml.etree.Element object

Serhiy Storchaka added the comment: lxml.etree classes don't implement any methods related to pickling: __reduce__, __reduce_ex__, __getstate__, __setstate__, __getnewargs__, __getnewargs_ex__. But there are extension classes which contain the state invisible to Python. In this case they are

[issue34894] Unexpected error while unpickling lxml.etree.Element object

Marcin Raczyński added the comment: How are you sure that a bug is not in the CPython implementation of the pickle module but in the lxml? -- resolution: third party -> status: closed -> open ___ Python tracker

[issue34894] Unexpected error while unpickling lxml.etree.Element object

Serhiy Storchaka added the comment: This is a tracker for bugs in the C implementation of Python. lxml is not a part of the Python standard library. Use corresponded bug trackers for reporting bugs in third-party packages. -- nosy: +serhiy.storchaka resolution: -> third party stage:

[issue34894] Unexpected error while unpickling lxml.etree.Element object

New submission from Marcin Raczyński : If we use pickle.HIGHEST_PROTOCOL we can pickle lxml.etree.Element object but unpickling give us misleading error description: >>> from lxml import etree >>> import pickle >>> import sys sys.version '2.7.15rc1 (default, Apr 15 2018, 21:51:34) \n[GCC 7.3.0]