-
Notifications
You must be signed in to change notification settings - Fork 119
Support Ironpython3.4 #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Ironpython3.4 #136
Conversation
Assigning m_app is apparently not required anymore in last RevitLookup versions and not even possible. Error: """python Traceback (most recent call last): File "<string>", line 83, in <module> File "<string>", line 63, in __init__ TypeError: can't set attributes of built-in/extension type 'CollectorExt' """
…er/patch-1 Fix set CollectorExt.m_app error
…ixcicd update version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Exciting!
One minor point: This is a breaking, backwards incompatible change. Python3 is for all intents and purposes a new language and anyone using RPS will have to update all their scripts. We should probably think hard about how to communicate this.
Any ideas? @eirannejad? @jeremytammik?
Maybe the new version can require a shebang header comment. Then it can assume that an old script lacking the comment or specifying a prior version of Python is for Python 2 or previous, try to convert it using 2to3 and explain the problem if that fails. Re. communication: I can post this on The Building Coder blog and in the Revit API discussion group. @eirannejad and others have lots of twitter followers, so we can try to spread the word there and on linkedin as well. Would that suffice? |
I recommend some document user need read after merge this commit to develop and release in master branch :
|
Hmm... the README.md file should probably also be updated (in this PR) to reflect the changes and @chuongmep 's links for further reading also integrated in that updated text. Since I won't be using this ever, I don't really have a lot of skin in the game. If the three of you are in agreement, I'm fine to merge. |
Hi @daren-thomas , updated to help people can follow with IronPython 3 😉 |
@chuongmep thank you very much! |
@daren-thomas, may be we need merge to master branch from develop to GitHub bot can publish a new version. |
sure. can you walk me through the process please? |
@daren-thomas I have create another pull request to do that, just need accept this : |
Purpose
This is an pull request support for Ironpython 3.4 release, we had wait along time to can do that.
Description
Declarations
Check these if you believe they are true
*.resx
filesReviewers
@daren-thomas @eirannejad
FYIs
@jeremytammik