David Cournapeau <cournape <at> gmail.com> writes: > > To answer your question, the main issues are: > - are two branches are necessary or not ? If two branches are > necessary, I think we simply do not have the resources at the moment. > - how to maintain a compatible C API across 2.x and 3.x > - is it practically possible to support and maintain numpy from 2.4 > to 3.x ? For example, I don't think the python 2.6 py3k warnings are > very useful when you need to maintain compatibility with 2.4 and 2.5. You should ask all those questions on the dedicated mailing-list: http://mail.python.org/mailman/listinfo/python-porting Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4