Read the next post up with instructions. It attaches them differently because they are in fact different
Pyrevit 4 CLI for pyrevit 4 on 2024 and lower
Pyrevit 5 CLI for pyrevit 5 on 2025
Edit:
I guess I could have been more clear on which pyrevit file to use for attaching to Revit…
These are the bin\pyrevit.exe within the pyrevit installation you are trying to attach, not a downloaded CLI.
You must either cd into the bin folder or preferably use the absolute path to the pyrevit.exe in case you have different versions on your system path. Added benefit is you can just pyrevit add this instead of having to write out the full path. This is a safer way to guarantee that you aren’t actually calling some other binary on system path with could break break attachment.
so cd in to pyrevit 4.6 installation bin folder and add/attach to 2024 and lower
then cd into pyrevit 5.0 installation bin folder and add/attach to 2025
Follow up question: how are you getting the WIP pyRevit onto your device, by running the WIP installer or other means?
I’m trying to figure out a way to roll out the WIP release to my firm (while keeping 4.8.16) though the the CLI and am hitting a brick with with the WIP releases only included the installer. Right now I’ll run the WIP installer on my device, and then create a git repo with the files in the installer destination folder & push it to GitHub, where I’ll then use the CLI to clone that repo with the WIP release.
When using the installer-installed release, Revit 2025 works just fine. However when cloning a copy of that release (using the 4.8.16 CLI), and then attaching to '25 (with the WIP CLI) on an endpoint computer, I get the below error.
Opening up the debug file for the Revit instance, I get the below output:
2024-09-25 14:36:53,138 ERROR [pyrevit.userconfig] Can not determine cpython engines for current attachment: Unknown | Product: "25.0" | Manifest: "C:\ProgramData\Autodesk\Revit\Addins\2025\pyRevit.addin"
I suppose this one question has drawn out to a couple, so to recap/conclude:
In your use case are you downloading using the WIP installer?
Does anyone know a better way of getting a WIP release onto & attached on a computer that doesn’t use the installer
This is available for testing/development purposes and there are outstanding issues including no working CLI yet.
only way to get 2025 attached (that I’ve found, and assuming nothing has changed since last week) is to use the WIP installer, CD into the bin directory in that installed location, and use specifically that pyrevit.exe file located there to attach 2025 only.
You can script the this using the wip installer same as the CLI, but probably better to keep this out of production env until its held together by more than duct tape and dreams.
heh, fair points all around. I’ve been pushing off the “when can we switch to Revit 25” question for a while - sounds like I’ll have to buy myself some more time too. Defiantly agree about not wanting to use a development release in prod. Thanks!
Thank you for the guide @jpitts!
It put me on track for setting it up for R2025 testing.
I sloved it slightly different, by installing 4.8 and 5.0 to different folders and then using:
Note, the path is not to the bin folder but the root folder.
I may have reinstalled pyRevit 4.8 after this and attached pyrevit5 clone to 2025 again, to solve an error (had to go back and forth with it a bit), but it works in all versions of Revit for me now.
The Pull Request has been merged and the new WIP install is working fine for all versions right now, I am going to stress test it this week and will report back. Thank you @sanzoghenzo
I downloaded the latest WIP 5.0.0.24309 ??? Installed it and got an error on opening Revit 2025, so I uninstalled that version and reinstalled 5.0.0.24229 again. It is still working in 2021-2025.
So maybe I got the wrong WIP? Can anyone provide a link for me? Thank you.
Jean-Marc, thank you very much! 5.0.0.24315 seems to be working great. I did have to uninstall everything and I even made sure to delete the pyrevit-master folder for good measure and then it worked fine. When I just tried to install it without uninstall first, it still gave an error in 2025.
I have version 5.0.0.24315, it seems to be working fine for the apps we use at least. The current WIP from https://www.pyrevitlabs.io/ is 5.0.0.24325. I presume it will also work with presumably a small bug fixed or something. I haven’t tried it out yet. But that is where you can get the latest WIP version.
Like I said above, I had to really uninstall and even delete the pyrevit-master folder to make sure and then it installed and worked fine. I think I’ll try out 5.0.0.24325 soon. We’ll see how things go.
@Jean-Marc
Are we able to pin a new topic at the top of the list? We should consolidate the latest instructions along with the WIP link for the installer to make it easily accessible.
Halfway-ish through this thread (scattered) seems to get you to all the information you need, but you wouldn’t know it by looking at the thread title, first post, or the accepted answer.