Release date Pyrevit 2025

Tools
41

WIP installer works for me on R2025.2!

thank you!

1 Like
42

you have to use the WIP installer for pyrevit v5 from this link

3 Likes
43

That works. Greatly appreciated. Thank you!

44

Great work all! Thanks so much for that. Much appreciated!

I was really excited to see this and immediately tried to install to give it a go and potentially help debugging, but for some reason I couldnā€™t get it to install.
I downloaded the pyrevit-installers folder from what I believe is the correct link and I just went through installing the 2 exe files in the (pyRevit_5.0.0.24232_admin_signed.exe and pyRevit_CLI_5.0.0.24232_admin_signed.exe).
Iā€™m not getting any error. Just when I open Revit 2025 I donā€™t get pyRevit in there.

Is anyone else having the same issue?
Am I doing it wrong?

1 Like
45

Hi @AndreaTas ,
Did you uninstall previous versions?
Please file in an issue on the repo with the text or the screen capture of the error.

I havenā€™t tried the admin installers, but will eventually tomorrow

46

Thanks @Jean-Marc for the prompt reply mate!

I did uninstall previous versions. After your reply I also tried with the non-admin installers to see if that was the issue and that still doesnā€™t work.

Although, unfortunately Iā€™m not getting any error and/or error messages. pyRevit just doesnā€™t show up after I install it. So weird!

Iā€™ll open an issue on GH now. I just thought of asking here before doing that, just in case I was doing something obviously wrong.

Thanks!

47

Weird, I did not see such an issue in the past 3 years after uninstall.
I installed the latest WIP installers many times around in the past weeks or so.

Could you try and remove also the pyrevit and pyrevit-master folders from %appdata% and program files if any before installing again

48

@Jean-Marc I did delete anything (files or folders) I could find in the %appdata% folder before installing.
I also tried again just to double-check and it still did not work.

49

The installer works for me with no issues. I can run it in Revit 2025.

50

No issues for me, but maybe uninstall the Forma add-in for Revit or disable it if not done already, that thing causes all sorts of issues for me with pyRevit loading.

As well as this try deleting the pyRevit folder in ProgramData if itā€™s still there between installs.

51

I had somebody else have similar issue. Manually placing the ini file in appdata and programdata fixed. edit to change the name of pyrevit installation to ā€œmasterā€ in the ini file

[environment]
clones = {"master":"C:\\Program Files\\pyRevit-Master"}
1 Like
53

Hello All.

Have tested pyRevit WIP release for Revit 2025 and all of my scripts seem to be working with no issues.
I have a quick question and I do apologize for asking it if someone already answered it - to install pyRevit for Revit 2025 I had to uninstall pyRevit for oldest Revit releases, does that mean I can only have pyRevit for Revit 2025 or Revit < 2025 at one time? Please advise.

54

Hi @VitalijM ,
The WIP installer should work with all revit versions!

2 Likes
55

Hey @sanzoghenzo, thatā€™s amazing! Thank you for the reply.

56

I just install pyRevit_5.0.0.24233 on my computer that had Revit 2023 & 2025.
My extension work fine on Revit 2023 but had some error on Revit 2025.

  1. In my WPF form that had Image Tag Name=ā€œimgā€. In python code
from System import Uri
from pyrevit.forms import WPFWindow
from pyrevit.framework import Imaging

class SteamFlow(WPFWindow):
    def __init__(self, element):        
        WPFWindow.__init__(self, "SteamFlow.xaml")
        self.img.Source = Imaging.BitmapImage(Uri(__file__.replace('SteamFlow_script.py','Formula.jpg')))

IronPython Traceback:
Traceback (most recent call last):
 File "C:\xxxx\xxxx\Mechanical.panel\Steam.pulldown\Steam Flow.pushbutton\SteamFlow_script.py", line 19, in <module>
ImportError: Cannot import name Uri

Now I fixed it by

import System
from pyrevit.forms import WPFWindow
from pyrevit.framework import Imaging

class SteamFlow(WPFWindow):
    def __init__(self, element):        
        WPFWindow.__init__(self, "SteamFlow.xaml")
        self.img.Source = Imaging.BitmapImage(System.Uri(__file__.replace('SteamFlow_script.py','Formula.jpg')))

I donā€™t know, this solution is good or not.

  1. In my WPF form used ListBox x:Name=ā€œFilterListBoxā€. In python code
from Autodesk.Revit.UI import ExternalEvent
from pyrevit import forms, revit
from pyrevit.forms import WPFWindow
from System.ComponentModel import ListSortDirection, SortDescription
from System.Windows.Data import CollectionViewSource

class ModelessForm(WPFWindow):
    def __init__(self, xamlfile, filters):
        WPFWindow.__init__(self, xamlfile)

        lvView = CollectionViewSource.GetDefaultView(self.FilterListBox.ItemsSource)
        lvView.SortDescriptions.Add(SortDescription("filtername", ListSortDirection.Ascending))

IronPython Traceback:
Traceback (most recent call last):
 File File "C:\xxxx\xxxx\General.panel\View Override.stack\Filter Visibility.pushbutton\script.py", line 22, in <module>
ImportError: Cannot import name ListSortDirection

Now I fixed it by

from Autodesk.Revit.UI import ExternalEvent
from pyrevit import forms, revit
from pyrevit.forms import WPFWindow
from System.ComponentModel import SortDescription
from System.Windows.Data import CollectionViewSource

class ModelessForm(WPFWindow):
    def __init__(self, xamlfile, filters):
        WPFWindow.__init__(self, xamlfile)
        lvView = CollectionViewSource.GetDefaultView(self.FilterListBox.ItemsSource)
        lvView.SortDescriptions.Add(SortDescription("filtername", 0))

I donā€™t know, whyā€™s Revit 2025 donā€™t find ENUM ListSortDirection.Ascending

57

Hi @hs0wkc, welcome to the community!

Please use the triple backticks (```) to enclose code and output messages for better readability; Iā€™ve done it for you this time :wink:

  1. Itā€™s perfectly fine to use that form of import.
  2. What was included in the .net framework System.dll is now split into multiple assemblies in .NET 8. In this case, the enum (and other things of the System.ComponentModel namespace) are moved to the System.ComponentModel.TypeConverter.dll assembly.

@dosymep @Jean-Marc should we track down everything that was included in the ā€œoldā€ libraries and add them to the assemblies to load? I wonder if we can bypass that list and provide all the loaded libraries directly from c#ā€¦

58

:disappointed_relieved: I apologizeā€¦ for my bad format.

1 Like
59

I opened an issue for that purpose just for now.

60

@Jean-Marc
Another thing that will need to be fixed is replace ā€œIntegerValueā€ property of ElementId with ā€œValueā€ for 2024+ (IntegerValue works in 2024 but is flagged Obsolete). This occurs extensively throughout pyrevitlib.

Iā€™ll start trickling in some pull requests for these as I come across them, but there quite a few

Edit:
And so I donā€™t forgetā€¦ Havenā€™t checked if any of these are used yet

2 Likes
61

You are right @jpitts I wanted to take care of that myself last year already.
If you donā€™t mind joining the effort.

thks