python dll search

[gswifort]

I think searching for the Python DLL file should look like this:

• if you are in a global environment, search in the path relative to RxLoader (or the main module):

  ..\..\..\python312.dll
  

• if you are in a virtual environment, from the file %VIRTUAL_ENV%\pyvenv.cfg, which looks like this:

  home = C:\Users\gswi\AppData\Local\Programs\Python\Python312
  include-system-site-packages = false
  version = 3.12.7
  executable = C:\Users\gswi\AppData\Local\Programs\Python\Python312\python.exe
  command = C:\Users\gswi\AppData\Local\Programs\Python\Python312\python.exe -m venv D:\Users\GSWI\Documents\PROGRAMY\demos\pyrx_pip_demo\venv

  take the value of home and there should be python312.dll

[CEXT-Dan]

That won’t work for AutoCAD .Bundle, nor will it work in my development environment.
A requirement is that the loader can be anywhere on the system

[gswifort]

But the ini file is still (and will be) supported? Maybe the path I described should be the standard one, and in other situations ini should be used?

[CEXT-Dan]

I had disabled most of the .INI stuff, only the stub path that’s in PyRxDebug.INI, this is copied into my debug folder by visual studio
However, it’s still a requirement that the loader can be anywhere on the system.

C++ development
developers may want their own solution
.Bundle

I guess I don’t understand what the problem is, to best recommend a solution.
Currently, if Python is not found in the PATH environment, then we search for AppData\Local\Programs\Python\Python312

[CEXT-Dan]

I suppose I can add it in, maybe

Search order:
......\python312
AppData\Local\Programs\Python\Python312
PATH

[CEXT-Dan]

Instead of using a hard relative path, I traverse parent paths until I hit python312

The order is:
tryFindPythonPathFromParent
tryFindPythonPathFromAppData
tryFindPythonPath

so in the logs, you should not see these if tryFindPythonPathFromParent is successful:
tryFindPythonPathFromAppData
tryFindPythonPath

[gswifort]

Log:
PyRxLoader::getPythonVenvPath 
PyRxLoader::thisModulePath d:\Users\GSWI\Download\pyrx_demo_temp\pyrx\pyrx\
PyRxLoader::getPythonVenvPath 
PyRxLoader::tryFindPythonPathFromParent 
PyRxLoader::tryFindPythonPathFromAppData C:\Users\gswi\AppData\Local\Programs\Python\Python312
PyRxLoader::getInstallPath C:\Users\gswi\AppData\Local\Programs\Python\Python312\Lib\site-packages\pyrx
PyRxLoader::tryFindWxPythonPath C:\Users\gswi\AppData\Local\Programs\Python\Python312\Lib\site-packages\wx
Loading PyRx from normal condition
PyRxLoader::PyRxLoader_loader Loading, C:\Users\gswi\AppData\Local\Programs\Python\Python312\Lib\site-packages\pyrx\PyRxZ25.0.Zrx

[CEXT-Dan]

The current behavior of tryFindPythonPathFromParent is to search for a parent folder “Python312”, assuming an install into Python312\Lib\site-packages

Log:
PyRxLoader::getPythonVenvPath
PyRxLoader::thisModulePath c:\users\dan\appdata\local\programs\python\python312\lib\site-packages\pyrx\
PyRxLoader::getPythonVenvPath
PyRxLoader::tryFindPythonPathFromParent c:\users\dan\appdata\local\programs\python\python312
PyRxLoader::getInstallPath c:\users\dan\appdata\local\programs\python\python312\Lib\site-packages\pyrx
PyRxLoader::tryFindWxPythonPath c:\users\dan\appdata\local\programs\python\python312\Lib\site-packages\wx
Loading PyRx from normal condition
PyRxLoader::PyRxLoader_loader Loading, c:\users\dan\appdata\local\programs\python\python312\Lib\site-packages\pyrx\PyRx24.3.arx
PyRxLoader_loader SUCCESS

[gswifort]

Ok, so this is just for the loader to find the main module..? So how can I point specifically to the location of python312.dll?

[gswifort]

ok, I think I know - PyRx.ini

[gswifort]

I want to deliver software to my coworkers. I don't want to rely on python in APPDATA, I want to have my own environment for pyrx. I want to add a specific file RxLoaderZ25.0.zrx to the startup list and have it search for the file PyRxZ25.0.zrx and python312.dll based on that. Searching for PyRxZ25.0.zrx works, although I would prefer it to first check if it is in the same directory as the loader.

[CEXT-Dan]

What about if you just name the folder Python312, with the same folder structure?
Users\XXX\Download\pyrx_demo_temp\Python312\normal-python-folder-structure, then tryFindPythonPathFromParent might work

Another option would be for me to add a cad env

(setenv "PYRX_PATH" "fullpath"), but it should have the same folder structure as Python312

[CEXT-Dan]

Pretty cool, a developer can just prepackage everything and send it off as a zip. Let me know how this works out

[gswifort]

Everything except python312.dll works

PyRxLoader::getPythonVenvPath 
PyRxLoader::thisModulePath d:\Users\GSWI\Download\pyrx_dist_test\Lib\site-packages\pyrx\
PyRxLoader::getPythonVenvPath 
PyRxLoader::tryFindPythonPathFromParent d:\Users\GSWI\Download\pyrx_dist_test
PyRxLoader::getInstallPath d:\Users\GSWI\Download\pyrx_dist_test\Lib\site-packages\pyrx
PyRxLoader::tryFindWxPythonPath d:\Users\GSWI\Download\pyrx_dist_test\Lib\site-packages\wx
Loading PyRx from normal condition
PyRxLoader::PyRxLoader_loader Loading, d:\Users\GSWI\Download\pyrx_dist_test\Lib\site-packages\pyrx\PyRxZ25.0.Zrx
PyRxLoader_loader SUCCESS
Polecenie: *Anuluj*
Polecenie: *Anuluj*
Polecenie: PYCMDPROMPT
>>>: import sys
>>>: print(sys.prefix)
c:\users\gswi\appdata\local\programs\python\python312   # ← ← ← ← ← ←

[CEXT-Dan]

Is Python in the env path? I reversed the search order for PATH in Commit 5e70f19

Command: PYCMDPROMPT
>>>: import sys
>>>: print(sys.prefix)
d:\mypyrx

[CEXT-Dan]

This is quite interesting from a deployment perspective.

I assume that Python does not need to be installed on the client system, is this correct?
The developer, can create a “package” by zipping up a minimal Python folder structure, with wxPython and PyRx, etc. the client can then simply unzip the package and load the loader.ARX?

Caveat, the client won’t easily be able to write scripts or use PIP, and it would fall on the developer to update their package, correct?
Another downside is a possible DLL conflict with other pyrx based applications, since there can only be one python312.DLL loaded. But that’s probably okay in some conditions, I.e. for large companies where deployment is rolled out by IT

[gswifort]

I'm doing something similar. I plan to include an embeddable version of python (with pip added) and my modules compiled into pyc files in the package. I want to leave users the option of writing their own scripts (e.g. loading everything placed in a specific location) and installing python packages. I'll let you know how it works when I'm done.

[gswifort]

I have these two files:

RxLoaderZ25.0.zrx
PyRxZ25.0.zrx

in one folder, but the main module does not load, probably because I do not have this directory in PATH..? Is it necessary?

PyRxLoader::getPythonVenvPath 
PyRxLoader::thisModulePath d:\Users\GSWI\Documents\PROGRAMY\fort_autocad_utils\dist\fort_cad_utils\_internal\pyrx\
PyRxLoader::getPythonVenvPath 
PyRxLoader::tryFindPythonPathFromParent d:\Users\GSWI\Documents\PROGRAMY\fort_autocad_utils\dist\fort_cad_utils\_internal
PyRxLoader::getInstallPath d:\Users\GSWI\Documents\PROGRAMY\fort_autocad_utils\dist\fort_cad_utils\_internal\Lib\site-packages\pyrx
PyRxLoader::tryFindWxPythonPath d:\Users\GSWI\Documents\PROGRAMY\fort_autocad_utils\dist\fort_cad_utils\_internal\Lib\site-packages\wx
Loading PyRx from normal condition
PyRxLoader_loader @find path FAILED

[gswifort]

If I understand correctly, the loader should add the wx directory to the PATH, in my case after loading there is only the pyrx directory in the PATH.

[gswifort]

Ok, the problem is probably that I built the distribution package from a python virtual environment. I'll test it further, but it seems that it is indeed best to create a clean, isolated from everything, environment from the python embeddable package.

[gswifort]

I would be grateful for a release with the current state of the repository.

[CEXT-Dan]

published [v2.2.1]

[gswifort]

Thank you!

[gswifort]

sys.prefix is set to global python installation even though PyRx theoretically loads the correct .dll. even if in CAD environment I add to ACAD and PATH the directory where python312.dll is located (c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal)

Polecenie: (LOAD "C:/Users/gswi/AppData/Local/Programs/FORT Polska/fort_cad_rx/fort_cad_rx_loader.lsp")
PyRx version <2.2.001.20250228> loaded:
Python Interpreter Loaded successfully!
File loaded: C:\Users\gswi\AppData\Local\Programs\FORT Polska\fort_cad_rx\_internal\pyrx\RxLoader24.1.arx

Polecenie:
Polecenie: PYRXLOADLOG

Log:
PyRxLoader::getPythonVenvPath
PyRxLoader::thisModulePath c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\pyrx\
PyRxLoader::getPythonVenvPath
PyRxLoader::tryFindPythonPathFromParent c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal
PyRxLoader::getInstallPath c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\pyrx
PyRxLoader::tryFindWxPythonPath c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\wx
Tue Mar 11 10:23:14 2025


Loading PyRx from normal condition
PyRxLoader::PyRxLoader_loader Loading, c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\pyrx\PyRx24.1.arx

PyRxLoader_loader SUCCESS

Polecenie: (getenv "ACAD")
"C:\\Users\\gswi\\AppData\\Local\\Programs\\FORT Polska\\fort_cad_rx\\_internal;C:\\Users\\gswi\\AppData\\Roaming\\Autodesk\\AutoCAD 2(...)"

Polecenie: (getenv "PATH")
"C:\\Users\\gswi\\AppData\\Local\\Programs\\FORT Polska\\fort_cad_rx\\_internal;C:\\Users\\gswi\\AppData\\Local\\Program(...)"

Polecenie: PYCMDPROMPT
>>>: import sys
>>>: print(sys.prefix)
c:\users\gswi\appdata\local\programs\python\python312

if before starting cad I set PATH to the directory where python312.dll is located then everything is ok

Polecenie: (LOAD "C:/Users/gswi/AppData/Local/Programs/FORT Polska/fort_cad_rx/fort_cad_rx_loader.lsp")
PyRx version <2.2.001.20250228> loaded:
Python Interpreter Loaded successfully!
File loaded: C:\Users\gswi\AppData\Local\Programs\FORT Polska\fort_cad_rx\_internal\pyrx\RxLoader24.1.arx

Polecenie:
Polecenie: *Anulowano*

Polecenie: *Anulowano*

Polecenie: PYRXLOADLOG

Log:
PyRxLoader::getPythonVenvPath
PyRxLoader::thisModulePath c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\pyrx\
PyRxLoader::getPythonVenvPath
PyRxLoader::tryFindPythonPathFromParent c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal
PyRxLoader::getInstallPath c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\pyrx
PyRxLoader::tryFindWxPythonPath c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\wx
Tue Mar 11 10:25:17 2025


Loading PyRx from normal condition
PyRxLoader::PyRxLoader_loader Loading, c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal\pyrx\PyRx24.1.arx

PyRxLoader_loader SUCCESS

Polecenie: (getvar "ACAD")
nil

Polecenie: (getenv "ACAD")
"C:\\Users\\gswi\\AppData\\Local\\Programs\\FORT Polska\\fort_cad_rx\\_internal;C:\\Users\\gswi\\AppData\\Roaming\\Autodes(...)"

Polecenie: (getenv "PATH")
"C:\\Users\\gswi\\AppData\\Local\\Programs\\FORT Polska\\fort_cad_rx\\_internal;C:\\Users\\gswi\\AppData\\Local\\Programs(...)"

Polecenie: PYCMDPROMPT
>>>: import sys
>>>: print(sys.prefix)
c:\users\gswi\appdata\local\programs\fort polska\fort_cad_rx\_internal

[CEXT-Dan]

with pyrx installed, but load from embedded

pip install cad-pyrx

Command: PYCMDPROMPT
>>>: import sys
>>>: print(sys.prefix)
d:\pyrx-embedded
---
Command: PYRXLOADLOG
Log:
PyRxLoader::getPythonVenvPath 
PyRxLoader::thisModulePath D:\pyrx-embedded\pyrx\
PyRxLoader::getPythonVenvPath 
PyRxLoader::tryFindPythonPathFromParent D:\pyrx-embedded
PyRxLoader::getInstallPath D:\pyrx-embedded\pyrx
PyRxLoader::tryFindWxPythonPath D:\pyrx-embedded\wx
Tue Mar 11 19:55:02 2025
Loading PyRx from normal condition
PyRxLoader::PyRxLoader_loader Loading, D:\pyrx-embedded\pyrx\PyRxZ25.0.Zrx
PyRxLoader_loader SUCCESS

[CEXT-Dan]

(getenv "ACAD") has no reference to pyrx
(getenv "PATH") nil

[gswifort]

I did (setenv "PATH", "") and it seems to work. I don't fully understand how setenv and getenv work in the CAD environment.

From my observations, it appears that:

1. it remembers this setting between sessions
2. it does not refer to the actual PATH environment variable

[gswifort]

Thank you. And sorry for my disability.

[CEXT-Dan]

In AutoCAD (getenv "PATH"), gets the actual “PATH” from ENV, so like 50 lines of stuff, so it’s different behavior that ZwCAD
When loading the loader, I push the paths to the module to the front of PATH, so it’s first in the search order. But It’s a local version of PATH

SetEnvironmentVariable
“Sets the contents of the specified environment variable for the current process.”

Something like (setenv "PYRX_LOG" "1") should create an entry in the profile section in the registry