-
Notifications
You must be signed in to change notification settings - Fork 119
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
IronPython installation breaks revitpythonshell #25
Comments
this has to do with the control used for the shell - avalon edit. it needs to be the same platform as Revit, otherwise it won't work. |
Can you please post a temporary fix? I am a beginner, and your comment does not make any sense to me. Now the Shell doesn't work after I installed IronPython :(. |
Uninstalling IronPython fixed the issue for now. |
Uninstalling is so far the only solution that I can find. I'm very sorry. If you install IronPython 2.7.3 (instead of 2.7.5) you should not have a On Wed, Mar 16, 2016 at 12:11 AM, shtirlitsDva [email protected]
|
Hi Daren -- not sure if this is related or not (sorry, I'm very new to RevitPythonShell and IPY as well) Will there every be any compatibility between RPS and IronPython 2.7.5? I only ask because I'm in dire need of the Requests module for IronPython, which only can be installed into 2.7.5 (primarily because 2.7.3 doesn't seem to support pip - the only way I understand out how to install Requests) -- naturally, I came across the same issue as above when I upgraded IronPython. Yes, this is a bizarre and irritating chain reaction of incompatibilities -- just curious if I should start looking for a workaround someplace here. |
actually, it might be possible to upgrade with revit 2017. but that could On Tuesday, 19 July 2016, jbuccola [email protected] wrote:
|
I'm actually not even able to download 2017 at the moment (freaks out our BIM manager). I've managed to work around things using .NET's library WebRequests instead -- far less elegant than the Requests module, but hey, it works. Might be re-writing my plugin this time next year... |
Original issue reported on code.google.com by
[email protected]
on 2 Feb 2015 at 6:13The text was updated successfully, but these errors were encountered: