I've received a confirmation that they are contacting PyAROS's donors, and some donations were already moved to the new bounty.

Great work, Power2People!

The representative said that PyAROS is an old project, but they should be able to contact most of the donors.

P.S. I saw my contribute now.

Yes, this is normal. I think the process is handled manually. Will the P2P contact the people in PyAROS bounty to have their money moved?

The bounty is open.

I've made a donation just a few minutes ago, but I don't see it yet. Is it normal?

It's still pending the question with the old PyAROS bounty. I have received not answer for this from the P2P representative.

Done, and sent the e-mail to the P2P representative.

Thanks to all for the support!

Ok, for me. Please also add this link to existing python ports:

https://github.com/ezrec/AROS-mirror/tree/ABI_V1/contrib/development/python

I've added the last part thanks to deadwood's feedbacks.

Please, pay attention also to the license paragraph, where I've added a reference to AROS-specific code, and the license that IMO should be used.

If everything is fine, tomorrow I'll forward this text to the P2P representative.




TITLE
Port Python 2.7 core to AROS


BODY
Python is a modern, simple, and very versatile language, which has a huge audience and is widely used in several projects, even of big multinationals like Google, IBM, Intel, etc..

Porting it to AROS not only brings a lot of software, but it allows to quickly create new ones too, and to better manage the system, since Python versatility goes from fast GUI applications prototyping to system administration, from testing to astronomical big data analysis, and so on. Python can be considered the Swiss knife of computer science.

Since the big effort required for the port, this bounty is the first of a series of 5 that will bring this language/platform to AROS. In fact, the port is ideally split in the following 5 parts:
- Python 2.7 core;
- PyZune (a complete Python binding for the Zune library);
- Python 2.7 external libs (bzip2, Berkeley db, openssl, sqlite3);
- Python 2.7 external libs (tcl, tk). This is optional or with a very low priority, since Tcl/Tk is used to build application with GUI, but for AROS the priority is making the same, albeit using Zune as natural and native replacement;
- Python 3.5.

For the bounty to be considered succeeded, Python 2.7 should run on at least 386 and x64 native builds of AROS, and all Python tests in the standard library (Lib/test/) must pass. Tests for different platforms/o.ses (Windows, Linux, etc.) should not necessarily pass, of course (if some passes, it's OK/welcome).

Python sources changes must be released when the bounty is completed. Python's PSF license must be used.

All new Python code must follow the PEP8 guideline. Only the AROS-specific code (not part of CPython) should follow the AROS coding style, and it should be released with the APL or a compatible license.

The last Python 2.7 version is 2.7.11, but if a new Python version is released then the bounty is considered to be updated with it. The Python version that should be implemented is "frozen" only after that the bounty is assigned.

There are already other old Python ports:

http://www.monkeyhouse.eclipse.co.uk/amiga/python/
http://pyaros.sourceforge.net/
https://bitbucket.org/yomgui/cpython/wiki/Home

however they are old, or for a different platform (the last is for MorphOS).

Albeit it's not required to start or use one of them for this AROS port, it's highly desirable to have only one port shared with MorphOS (last link), because the two o.ses are very similar and most of the code can be shared.

Integration of this Python port with the AROS build system is warmly appreciated, but it's not required by the bounty.

Also as an optional requirement I would suggest integrating with AROS build system (so that it appears in nightlies). However only optional.

Quote:

I would mention them in the bounty description as person taking it might not be aware about the, but would not require them to be used.

I specified x86 and x64 only for testing the code. I think it's a bit overkill asking the submitter to test every supported AROS platform: it's already difficult setting-up a single system.

However when the work is done, and the bounty is in the code review process, who is interested on testing other AROS configurations, can setup the system and test itself.

I want to stress one point regarding this bounty: it's quite unlikely that CPython (Python's mainstream distribution) doesn't work on some architecture. I haven't seen specific piece of code which can break on some processor and work well only on some others.

Albeit it's quite complex, CPython is an application and not a game or a driver, etc., where the chance of hitting hard on low-level stuff is sensible.

In the good and in the evil, because this approach has its limits in the efficiency of the virtual machine.

That's why I've created WPython, which IS sensible to such low-level stuff (however I was a polite guy, using macros for handling big and little-endian data ). But this bounty is related to CPython, and not WPython.