Dong-hee Na donghee.na92 at gmail.com
Fri Nov 17 11:56:06 EST 2017

• Previous message (by thread): [Python-Dev] unittest isolation and warnings
• Next message (by thread): [Python-Dev] Clarify the compatibility policy of lib2to3.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hi, 

Few days ago, I submitted a patch(https://github.com/python/cpython/pull/4417) which updates2to3 converts `operator.isCallable(obj)` to `isinstance(obj, collections.abc.Callable)`.

This was Serhiy Storchaka’s idea(https://bugs.python.org/issue32046) and I agree with his idea since `callable` is not available in all 3.x versions.

However, some people would like to clarify the policy of 2to3.
That means that 2to3 is compatible with the branch that is currently maintained? or it is converted to specific Python 3.X codes with the specific version of 2to3?

Cordially,
Dong-hee
—
Dong-hee Na
Chungnam National University | Computer Science & Engineering

Tel: +82 010-3353-9127
Email: donghee.na92 at gmail.com
Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/
Github: https://github.com/corona10

---

• Previous message (by thread): [Python-Dev] unittest isolation and warnings
• Next message (by thread): [Python-Dev] Clarify the compatibility policy of lib2to3.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list