Changeset 1106

Timestamp:

03/13/21 00:50:05 (4 years ago)

Author:

Maciej Komosinski

Message:

Since 5.0rc19 there is no need to restore the current working directory because Framsticks does not change it

File:

• framspy/frams.py (modified) (3 diffs)

framspy/frams.py

@@ -302 +302 @@
                 print("*** Could not find or open '%s' from '%s'.\n*** Did you provide proper arguments and is this file readable?\n" % (lib_name, os.getcwd()))
                 raise
-        os.chdir(original_dir) # restore current working dir after loading the library so framsticks sees the expected directory
+        os.chdir(original_dir)  # restore current working dir after loading the library so Framsticks sees the expected directory
 
         c_api.init.argtypes = [ctypes.c_int, ctypes.POINTER(ctypes.c_char_p)]
@@ -345 +345 @@
         c_args = (ctypes.c_char_p * len(initargs))(*list(a.encode(ExtValue._encoding) for a in initargs))
         c_api.init(len(initargs), c_args)
-        os.chdir(original_dir) # restore current working dir again, because framsticks changes dir to 'data'
+
         Root = ExtValue._rootObject()
         for n in dir(Root):
@@ -353 +353 @@
                                 attr = attr._value()
                         setattr(sys.modules[__name__], n, attr)
+                        
         print('Using Framsticks version: ' + str(Simulator.version_string))
         print('Home (writable) dir     : ' + home_dir)