Aha. The annoying thing with this patching approach is that you cannot make changes to the baseline without invalidating all the patches. I suppose they must have a private branch somewhere which they use to generate the .patch files.
Regarding switching: I noticed this when I was woking on my tealet project (https://bitbucket.org/stackless-dev/tealet) . I took the switching code from the greenlet project. There are differences with Stackless, but it isn't always clear which is the more up-to-date version. Also, some of the platforms supported look rather outmoded. What we want to focus on, I suppose, is Win32, Win64, i686 and x86_64 (win and linux intel cpus) plus arm.... Theoretically, we probably should differentiate between arm and armhf, since we should save and restore floating point registers. I tried to be careful with that in the x64 port that I did for windows back in the days... K On 2 April 2015 at 12:25, Jeff Senn <s...@maya.com> wrote: > Kivy still does this (though I suppose they branched the original > PythonForAndroid) -- only the patches are pretty minor (mostly build stuff > and a few changes here ad there for platform problems -- Android is not too > bad as it is Linux natively). The same is true of Kivy's iOS python > (different patches of course). > > One other thing I noticed (in my occasional cross-platform foray): the > stackless codebase probably should get a review of the platform-specific > switching code at some point -- the Greenlet project ( > https://github.com/python-greenlet) originally a spinout of Stackless, > has improved platform switching code (in terms of number of platforms and > ease of building). > > On Apr 2, 2015, at 6:16 AM, Kristján Valur Jónsson <swesk...@gmail.com> > wrote: > > Interesting. The last time I looked, (some 18 months ago) kivy (for > android) was using "PythonForAndroid". > This was a strange beast, being built bu pulling a particular revision of > Python2.7 and applying a bunch of "patches" to it before compiling it. > My thought at the time was to try to merge those patches into a proper > Stackless Python branch, and thus make Stackless the python of choice for > Android and IOS. > Sadly, I didn't have the time for such a project. > Now, it appears PythonForAndroid has morphed into QPython or something.... > > > On 19 March 2015 at 18:26, Jeff Senn <s...@maya.com> wrote: > >> >> >> I have a patch that switches out the python with stackless for iOS (and >> hopefully soon Android). I haven't done much testing yet though. >> >> I > > _______________________________________________ > Stackless mailing list > Stackless@stackless.com > http://www.stackless.com/mailman/listinfo/stackless > > > > _______________________________________________ > Stackless mailing list > Stackless@stackless.com > http://www.stackless.com/mailman/listinfo/stackless >
_______________________________________________ Stackless mailing list Stackless@stackless.com http://www.stackless.com/mailman/listinfo/stackless
