Skip to content

Added Python 3.5 Support - #104

Closed
brisingraerowing wants to merge 1 commit into
pythonnet:developfrom
brisingraerowing:develop
Closed

brisingraerowing wants to merge 1 commit into
pythonnet:developfrom
brisingraerowing:develop

Conversation

@brisingraerowing

Copy link
Copy Markdown

I added preliminary Python 3.5 support. A quick test (getting some properties from the System.Environment class) worked perfectly fine on Windows 10 x64 with Python 3.5.0 amd64.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be guarded with a condition on DefineConstants not being already set. Otherwise the ReleaseWin|x64 target will always try and build the Python 3.5 build, regardless of the settings passed in via setup.py.

This line can probably just be removed (see line 47 just above here).

@tonyroberts

Copy link
Copy Markdown
Contributor

@brisingraerowing thanks very much for doing this. I've added a few comments to the code for you to look at. In addition, I think it would be good to add 3.5 to the travis and appveyor CI builds and run the unit tests before we integrate this.

@fdanny fdanny mentioned this pull request Oct 1, 2015
@filmor

filmor commented Oct 2, 2015

Copy link
Copy Markdown
Member

Why was this closed?

@den-run-ai

Copy link
Copy Markdown
Contributor

How can this unknown branch get forked to continue Python 3.5 work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants