
On Fri, 18 Aug 2017 at 02:05 Christian Tismer <tismer@stackless.com> wrote:
Hi friends,
in the last months, I have developed signature support for PySide. The module creates the same signatures as are known for plain Python functions.
As a non-trivial addition, the module also handles multiple signatures as a list. I consider this extension to PySide as quite essential and actually more important as for Python itself, because type info is rather crucial for PySide.
Initially, I wrote this as a pure Python 3 extension. Then I was "asked" to port this to Python 2 too, which was quite hairy to do. I'm not sure if I should have done that.
Before I publish this module, I want to ask: --------------------------------------------
Is it a bad idea to support signatures in Python 2 as well? Do I introduce a feature that should not exist in Python 2? Or is it fine to do so?
Please let me know your opinion, I am happy with any result.
If you're getting paid to do the port then I don't think it really hurts anything since it isn't going to magically open Python 2 to more usage. In fact, if you are filling in the annotation information so that type hints are being exposed then maybe there's a chance it might help someone port to Python 3?