PYTHONPATH not working as intended on OS4

	Bottom Previous Topic Next Topic
Register To Post

rjd324

Posted on: 2022/10/23 12:48 #1

Quite a regular

RAM:test.py:


import runpy



if __name__ == "__main__":

    print "Hello"

Ensure there is no value set for PYTHONPATH at the moment:


getenv PYTHONPATH

# should result in nothing

Execute the script:


python test.py

# "Hello"

Set PYTHONPATH:


setenv PYTHONPATH workbench:

# or any location

Ensure that it has been set:


getenv PYTHONPATH

# workbench:

Execute the script:


python test.py

'import site' failed; use -v for traceback

Traceback (most recent call last):

  File "test.py", line 1, in <module>

    import runpy

ImportError: No module named runpy

Try also in "sh" - the same issue.

I report this because on OS4Depot it is version 2.4.1, but somehow I have 2.5.6 and I cannot remember where I got that from. I am not sure if 2.5.6 was meant to be more mature than 2.4.1 or whether this is a known issue.

PYTHONPATH is meant to extend - not replace - the searchables.

Anonymous

Re: PYTHONPATH not working as intended on OS4

@rjd324

That might be the problem i'm getting with most (if not all) of python scripts...

How did you work around it?
Remove PYTHONPATH completely?

rjd324

Re: PYTHONPATH not working as intended on OS4

Posted on: 2022/10/23 12:56 #3

Quite a regular

I noticed it when invoking a "configure". In the configure it runs a python script and sets PYTHONPATH - now, the native modules installed in Workbench are not visable.

I am working on the configure script now, but I would guess it is going to have to be a hack to also add the native OS4 modules path - as well as - the additional path wanted by the configure script.

rjd324

Re: PYTHONPATH not working as intended on OS4

Posted on: 2022/10/23 12:57 #4

Quite a regular

Since there is no github location, I cannot report an official bug.

Anonymous

Re: PYTHONPATH not working as intended on OS4

@rjd324

I have this
Quote:

SYS:System/Python/Lib

in my PYTHONPATH ENVvar.

Trying to get rid of it and see if the python scripts behave again

Anonymous

Re: PYTHONPATH not working as intended on OS4

@rjd324

...and yes it does

flawfinder running fine now

Thanks a lot for the hint...

...and now that you mention it, i had a similar problem with PKG_PATH (or something like that), it refused to find perfectly available .pc files while configuring...after the updated SDK was installed, i removed everything SDK related from ENVARC first and the PKG_PATH var wasn't created and i haven't had a hit since...

Seems there is something wrong with adding pathes from envvars?

rjd324

Re: PYTHONPATH not working as intended on OS4

Posted on: 2022/10/23 13:43 #7

Quite a regular

Great news.

At least we know of that bug. Manipulation of PYTHONPATH (and friends) is quite common for PY stuff; even I know that I am by far an expert in PY.

If we had access to the source code for PY2.5.6 we could perhaps have a look and fix it - versus: porting PY from scratch when someone has clearly already done most of the hard work.

rjd324

Re: PYTHONPATH not working as intended on OS4

Posted on: 2022/10/23 13:59 #8

Quite a regular

For the sake of completeness and history:

See also: https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=4187

Register To Post
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )