Import fails on updating changes in nested import python module

[Walter Rojas]

 

1. Routinely I import (level 1) a py module (level 2) that, in turn,
   imports another module (level 3).
2. I've been making changes for weeks to the level 3 module and those
   were reflected in VW until now.
3. Suddenly VW2023 stopped to detect changes to the
   level 3 module; I tried to fix resetting script's paths with no success.
4. The solution was to use the importlib module in the level 2 script
   to force the reloading of the level 3 module: import utilerias
    

import importlib
import utilerias
importlib.reload(utilerias)

 

Hope it helps.

Edited March 29, 2023 by Walter Rojas

[JBenghiat]

Yes, this is known/expected.  Vectorworks preserves the Python session and caches any imports. There’s been a couple threads on the subject:

 

[Walter Rojas]

hace 9 minutos, JBenghiat dijo:

Yes, this is known/expected.

Zen advice: To live with no expectations.

Thanks for your patience.