Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Eli Bendersky
2013/1/1 Eli Bendersky eli...@gmail.com: Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define their name similarly to the Python version in their PyTypeObject. Some examples: Decimal, xml.etree's Element. Others prepend an

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Benjamin Peterson
2013/1/3 Eli Bendersky eli...@gmail.com: 2013/1/1 Eli Bendersky eli...@gmail.com: Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define their name similarly to the Python version in their PyTypeObject. Some examples:

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Eli Bendersky
On Thu, Jan 3, 2013 at 6:43 AM, Benjamin Peterson benja...@python.orgwrote: 2013/1/3 Eli Bendersky eli...@gmail.com: 2013/1/1 Eli Bendersky eli...@gmail.com: Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Benjamin Peterson
2013/1/3 Eli Bendersky eli...@gmail.com: etree has a C accelerator that was improved and extended in 3.3 and was made the default when importing etree. But a regression (issue #16076) occurs because _elementree.Element has no pickling support, while the Python version does by default (being a

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Eli Bendersky
On Thu, Jan 3, 2013 at 6:50 AM, Benjamin Peterson benja...@python.orgwrote: 2013/1/3 Eli Bendersky eli...@gmail.com: etree has a C accelerator that was improved and extended in 3.3 and was made the default when importing etree. But a regression (issue #16076) occurs because

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Stefan Krah
Eli Bendersky eli...@gmail.com wrote: Yes, of course. All of that is already implemented in patches Daniel Shahaf has submitted to the issue. The controversial question here is whether it's valid to change the __module__ of the type between 3.3 and 3.3.1 ? In 3.2 and in the Python version

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-03 Thread Benjamin Peterson
2013/1/3 Eli Bendersky eli...@gmail.com: On Thu, Jan 3, 2013 at 6:50 AM, Benjamin Peterson benja...@python.org wrote: 2013/1/3 Eli Bendersky eli...@gmail.com: etree has a C accelerator that was improved and extended in 3.3 and was made the default when importing etree. But a

[Python-Dev] PyTypeObject type names in Modules/

2013-01-01 Thread Eli Bendersky
Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define their name similarly to the Python version in their PyTypeObject. Some examples: Decimal, xml.etree's Element. Others prepend an understore, like _pickle.Pickler and many others. What are the

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-01 Thread Benjamin Peterson
2013/1/1 Eli Bendersky eli...@gmail.com: Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define their name similarly to the Python version in their PyTypeObject. Some examples: Decimal, xml.etree's Element. Others prepend an understore, like

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-01 Thread Eli Bendersky
On Tue, Jan 1, 2013 at 8:15 AM, Benjamin Peterson benja...@python.orgwrote: 2013/1/1 Eli Bendersky eli...@gmail.com: Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define their name similarly to the Python version in their PyTypeObject.

Re: [Python-Dev] PyTypeObject type names in Modules/

2013-01-01 Thread Benjamin Peterson
2013/1/1 Eli Bendersky eli...@gmail.com: On Tue, Jan 1, 2013 at 8:15 AM, Benjamin Peterson benja...@python.org wrote: 2013/1/1 Eli Bendersky eli...@gmail.com: Hello and happy 2013, Something I noticed earlier today is that some C versions of stdlib modules define their name