Message236857
Ok, if I don't finish it today, I *will* finish it tomorrow. Or Sunday. Sunday is the latest, though I'm pretty sure I'll be done by Saturday.
Hardest part is likely going to be re-configuring the Android emulator to test it.
Cyd (and anyone else who can), do you think you could test the binaries, too? I'll get them to you somehow. You have a real device; I have an old real device and an emulator.
Side note for Cyd: I'd advise you just use the fork of CPython you have and just push them to GitHub:
$ git remote add origin <url of your GitHub repo with .git at the end>
$ git push --all origin -u
That will push your changes (and every branch of CPython, I have no clue what your branch name is, so this just does everything) to the GitHub mirror.
So...I'm understanding that the game plan will go like this:
- Cyd pushes the changes he made to a GitHub fork of Python (and hopefully posts the URL here ;)
- I clone the repo and try to get the changes working with the dev version
- Somewhere in between now and the end of the world, Ethan will set up a build slave
I'll also help all I can with keeping these changes working with future versions of Python. |
|
Date |
User |
Action |
Args |
2015-02-27 23:26:51 | refi64 | set | recipients:
+ refi64, vstinner, r.david.murray, skrah, freakboy3742, ethan.furman, chaselton |
2015-02-27 23:26:51 | refi64 | set | messageid: <1425079611.03.0.0381106094342.issue23496@psf.upfronthosting.co.za> |
2015-02-27 23:26:51 | refi64 | link | issue23496 messages |
2015-02-27 23:26:50 | refi64 | create | |
|