You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah we certainly can do. I started getting that ready in another branch, but I was going to hold off putting anything into develop as I'd thought we wanted to do a release that was pretty much the same as where the old sourceforge version left off -- but getting it working with 3 before 2.0 sounds good to me.
I'm away for a few days, but will pick this up again next week.
How is python 3 support? I would love to get to a place where 'pip install --pre pythonnet' just works in a python 3 envrionment. Anything I can do to help?
I'm actually in the middle of rebasing that fork onto the
pythonnet/pythonnet fork (which was created after, but directly from the
svn repo and so there's no common root) with all the changes in a new
python3 branch. If you want to have a look at that it's here: https://github.com/renshawbay/pythonnet_new
Both branches are working, but I'm hoping to drop the first in a favor of
the new one soon (which will then be much easier to keep up to date with
the pythonnet/pythonnet fork, and will be easier to integrate at some
future point).
How is python 3 support? I would love to get to a place where 'pip install
--pre pythonnet' just works in a python 3 envrionment. Anything I can do to
help?
—
Reply to this email directly or view it on GitHub #12 (comment).
The python3 branch (https://github.com/renshawbay/pythonnet) has now been rebased on the main pythonnet repo so it's not in too bad shape. The newer features that I'd like to see in 2.0 are in that branch too (subclassing .net classes in python etc). Everything in that branch is unittested and working for python 2, but there are some problems with some of the tests for python 3 still (see build status on the other fork's page). The 3.2 x64 build is what I'm currently using, which is working fine for me (and passing all unittests). I'll keep chipping away at the remaining problems as time permits, but unfortunately it's not a priority for me at the moment. If you want to dive in and take a look at any of the remaining issues please do, I'm always happy to review/merge pull requests!
Activity
davidanthoff commentedon Mar 12, 2014
This probably should be sorted for 2.0, right?
tonyroberts commentedon Mar 12, 2014
Yeah we certainly can do. I started getting that ready in another branch, but I was going to hold off putting anything into develop as I'd thought we wanted to do a release that was pretty much the same as where the old sourceforge version left off -- but getting it working with 3 before 2.0 sounds good to me.
I'm away for a few days, but will pick this up again next week.
davidanthoff commentedon Mar 13, 2014
Good point, lets stick to the original plan and do this for version 2.1 or something like that.
adamklein commentedon Nov 7, 2014
How is python 3 support? I would love to get to a place where 'pip install --pre pythonnet' just works in a python 3 envrionment. Anything I can do to help?
tonyroberts commentedon Nov 7, 2014
You can get a working python 3 (as well as 2) fork from here:
https://github.com/renshawbay/pythonnet
and build it with setupwin.py.
I'm actually in the middle of rebasing that fork onto the
pythonnet/pythonnet fork (which was created after, but directly from the
svn repo and so there's no common root) with all the changes in a new
python3 branch. If you want to have a look at that it's here:
https://github.com/renshawbay/pythonnet_new
Both branches are working, but I'm hoping to drop the first in a favor of
the new one soon (which will then be much easier to keep up to date with
the pythonnet/pythonnet fork, and will be easier to integrate at some
future point).
cheers.
Tony
On Fri, Nov 7, 2014 at 4:18 PM, Adam Klein notifications@github.com wrote:
hognala commentedon Feb 10, 2015
How's the python 3 and general version 2.0 work going?
tonyroberts commentedon Feb 10, 2015
The python3 branch (https://github.com/renshawbay/pythonnet) has now been rebased on the main pythonnet repo so it's not in too bad shape. The newer features that I'd like to see in 2.0 are in that branch too (subclassing .net classes in python etc). Everything in that branch is unittested and working for python 2, but there are some problems with some of the tests for python 3 still (see build status on the other fork's page). The 3.2 x64 build is what I'm currently using, which is working fine for me (and passing all unittests). I'll keep chipping away at the remaining problems as time permits, but unfortunately it's not a priority for me at the moment. If you want to dive in and take a look at any of the remaining issues please do, I'm always happy to review/merge pull requests!
Merge pull request #78 from renshawbay/python3
tonyroberts commentedon Jun 26, 2015
Done in 138bda7