IronPython 3.4.0

Runtime
7

Is this only me or link is broken :grinning:?

8

@Konstantin you’re right
on the repo, go to Actions, then pick the latest build from develop branch and download installers

image
image1358×2261 212 KB

OR

  1. using the CLI clone the develop branch
    pyrevit clone <clone_name> [--dest=<dest_path>] [--source=<repo_url>] [--branch=<branch_name>]
  2. attach it to your revit versions
    pyrevit attach nameOfYourClone 340 --installed
3 Likes
9

Poof sorry. I apparently fogot to put the link there. Updated to the lasted WIP build link right now.

Thanks @Jean-Marc for the answer and screenshots :smiley:

3 Likes
10

Thanks! That helped :slightly_smiling_face:

11

Hi @eirannejad, I feel a certain excitement, but I am not sure what the additional features or benefits are yet compared to CPython or IronPython 2.X :flushed:?

I tried looking at the IronPython 3.4 release notes, but this also didn’t enlighten me. Does this allow us to run pyRevit scripts using both Python 3.4 libraries and pyRevit modules?

12

Hi @GooseG!

Try these notes:

https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython30.md
https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython31.md
https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython32.md
https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython33.md
https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython34.md
https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython35.md
https://github.com/IronLanguages/ironpython3/blob/master/WhatsNewInPython36.md

tick marks means already implemented. e.g. for IronPython 3.4 there is already f-string feature, even it is only available since python 3.6

I am personally very excited about ipy3, and looking forward to switch to it. Testing it now. Feels like I sit in a new car :grinning:

2 Likes
13

from the other hand, there is no tick next to enum module, but the module is in the library, we can import it now.
then I have no idea what these tick-marks mean :sweat_smile:

mystery. gotta try one by one:
image

14

@GooseG IronPython has its own merits, namely:

  • Compilable to dotnet DLLs
  • True multi-threading (CPython has a global interpretter lock (GIL) that forcefully syncs threads so the multi-threading performance in IronPython is better)

CPython and IronPython, althought both python 3, implement it completely differently and they’re just different beasts.

Your existing pyRevit scripts should run nicely in the new IronPython 3 with the added benefit that you can completely forget about python 2 (python 3 has much more powerful language constructs and libraries)

Use CPython when you’d need to use any of “native” libraries built for CPython e.g. numpy, scipy etc

3 Likes
15

I have some wpf so I cannot use cpython
but I also want to use numpy
is it possible???

16

You have to use WPF purely programmatically. CPython doesn’t have WPF bindings yet

1 Like
17

so sad :frowning:
how about winform + numpy instead of wpf?
seems I can use winform on cpython

18

That’s an option as well. There is also the cross-platform Eto library that could be used programmatically.

1 Like
19

Hi guys!
I’ve started getting errors.
How do I report them? Just make an issue in repository? Any special name?

20

yep, issue in the repo, following the template.
you can prefix it IPY340 maybe?

2 Likes
21
1 Like
22

Hi! Just installed your WIP. But now I can’t save chosen version of Iron Engine

24

@eirannejad hi! I installed that but every time I try to save ironpython3 as an engine and open settings again - there is 277 again. I tried also to edit the pyRevitfile and change the chosen element to ironpython 340 - copying the path and version from iron python 340. In this case pyRevit doesn’t work and shows this when restarting Revit

pyrevitc
pyrevitc1414×1178 333 KB

25

Do we have an overview of what issues 3.4 still has as pyRevit engine? Can only find one here. Keen to help further bring it to life.

26
1 Like