On Tuesday 02 April 2013 19:41:02 Jakub Jermar wrote:
> > Then boot HelenOS and enjoy Python!
> 
> and Python I enjoyed! Thanks for working on this.

Welcome. I guess it's time to work on something more serious now ;)

> How do you get the new binary and the python2.7 library to the
> initrd.img? For me, this was not very convenient as I had to prevent
> make in the boot subtree from cleaning up uspace/dist first.

I made some nasty ad-hoc hack to the Makefile.

> I used the new 4.8 toolchain to build Python and it produced a great
> deal of warnings, fortunately the compilation completed just fine.

Yeah, but it actually has almost all possible warnings enabled and it's not 
much different from Python compilation for Linux with the same flags, although 
probably there are some extra warnings worth fixing.

> I also found the warnings emitted by posix_sigaction() quite annoying,
> perhaps we could silence the warnings somehow.

Agreed.

> So, could you sum up the current status as far as features and
> limitations are concerned (besides those that you already mentioned).

I didn't mention that there is no dynamic loading of C modules (but I guess it 
is expected/obvious) and every C module needs to be compiled-in to be used. At 
the moment number of compiled-in modules is rater small, but they may be added 
if there is a need to do so.
And of course the port is not well tested yet.

> What would be the next steps to proceed from here?

The first thing to do is to implement missing floating point functions, as the 
lack of them extremely restricts usability.
After that it needs some testing (I haven't even tried to run Python test 
suite yet, as it's pointless without a proper floating point support).
When we have proper tests we will see what is broken and what needs to be 
fixed.
Also I'm going to look at that close in file object destructor issue.
The other thing I'm going to do is to backport fix for 
http://bugs.python.org/issue17610 (Python guys are amazing, the bug was fixed 
the same day I filled the report!) to Python 2.7 and use this fix instead of 
current hack (not that it's important from practical point of view, but it 
feels the right thing to do).

I could list a few more things, but doing the above will be a good start.

I also encourage people to try it out.

> The patches look reasonably small and the overall amount of changes is
> pretty small too, which is nice. Unless someone has some serious
> concerns, I would like to integrate this.

Great, thank you!

Zbigniew

_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel

Reply via email to