output.print_md crashes revit2023 (pyrevit 4.8.14.24016)
jj-github-jj opened this issue · 4 comments
✈ Pre-Flight checks
🐞 Describe the bug
This script crahses Revit2023. The first 2 lines (import and output=script.get_output() do not create issues but the
third line which has output.print_md crashes it
from pyrevit import script
output = script.get_output()
output.print_md('#Hello World ')
♻️ To Reproduce
Steps to reproduce the behavior:
Run the 3 line script as a pushbutton script using pyrevit using the ironpython 3.4 setting in pyrevit configuration
⏲️ Expected behavior
No crash
🖼 Screenshots of the issue
🖥️ Hardware and Software Setup (please complete the following information)
- Windows version 10
- pyRevit Version 4.8.14.24016
- pyRevit Environment: ironpython 340 script
==> Registered Clones (full git repos)
==> Registered Clones (deployed from archive/image)
master | Deploy: "basepublic" | Branch: "master" | Version: "4.8.14.24016+1909" | Path: "C:\Users\user\AppData\Roaming\pyRevit-Master"
==> Attachments
master | Product: "24.1.1" | Engine: IPY340PR (340) | Path: "C:\Users\user\AppData\Roaming\pyRevit-Master"
master | Product: "23.1.3" | Engine: IPY340PR (340) | Path: "C:\Users\user\AppData\Roaming\pyRevit-Master"
master | Product: "2021.1.9" | Engine: IPY340PR (340) | Path: "C:\Users\user\AppData\Roaming\pyRevit-Master"
==> Installed Extensions
TEESI | Type: Unknown | Repo: "" | Installed: "T:\MASTER\Revit\TEESI Revit Add-Ins\Teesi Tools\ScriptsStaging\TEESI.extension"
==> Default Extension Search Path
C:\Users\user\AppData\Roaming\pyRevit\Extensions
==> Extension Search Paths
T:\MASTER\Revit\TEESI Revit Add-Ins\Teesi Tools\ScriptsStaging
==> Extension Sources - Default
https://github.com/eirannejad/pyRevit/raw/master/extensions/extensions.json
==> Extension Sources - Additional
==> Installed Revits
24.1.1 | Version: 24.1.10.25 | Build: 20230830_0315(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2024"
23.1.3 | Version: 23.1.30.97 | Build: 20230828_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2023"
2021.1.9 | Version: 21.1.90.15 | Build: 20230907_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2021"
==> Running Revit Instances
PID: 44860 | 23.1.3 | Version: 23.1.30.97 | Build: 20230828_1515(x64) | Language: 0 | Path: "C:\Program Files\Autodesk\Revit 2023"
==> User Environment
Microsoft Windows 10 [Version 10.0.19045]
Executing User: TEESI\user
Active User: TEESI\user
Admin Access: No
%APPDATA%: "C:\Users\user\AppData\Roaming"
Latest Installed .Net Framework: 4.8
No .Net Target Packs are installed.
No .Ne-Core Target Packs are installed.
pyRevit CLI v4.8.14.24016+1909.ee814ee2f686d23db8bb6ff80d8bb918ff9adc99
please fill out all the requested info. The template is there to guide you to provide us useful information that can make the resolution of the issue much quicker.
writing "ironpython script" under the "pyrevit Environment" voice is not gonna help us in any way, please take your time and post the pyevit env output there.
Is the error message? or it just exits without even a crash log?
And for clarification: the default ironpython environment is 2.7.11, not 3.4. Does it crashes with both versions of the engine?
@sanzoghenzo sorry that I typed ('default') but the env is ironpython 3.4 . I have updated the bug report to include the previt env output. Didnt know about that feature and if it was already in the bug template, I missed it but now I know so thanks for the info.
Is there an error message? or it just exits without even a crash log?
@jj-github-jj can you please answer these questions? if there's an error message, post it here as it will greatly help us understand the cause.
Never mind, I tested it and I can reproduce it: when I click the button I can see a spinning circle cursor, and after some time Revit exits without messages. Journals don't show anything and no crash dump is produced (at least I couldn't find anything).
I'm sorry I won't be able to help fixing this issue, I'm focused in resolving the CPython compatibility instead of trying to make this version of the engine work.
You're better off staying with the default 2.7.11 engine for the time being