Should I take care of "could not determine Graal.Python's *** path"?

[eomasters-repos]

When I enable verbose logging, I see the following lines:

[python::Python3Core] FINE: Initial locations:
	Language home: null
	SysPrefix: 
	BaseSysPrefix: 
	CoreHome: 
	StdLibHome: 
	CAPI: 
	JNI library: 
	Home candidate: C:\Users\marco\.snap\auxdata\eomtbxpro\graalpy\bin
[python::Python3Core] FINE: Updated locations:
	Language home: C:\Users\marco\.snap\auxdata\eomtbxpro\graalpy\bin
	SysPrefix: 
	BaseSysPrefix: 
	CoreHome: 
	StdLibHome: 
	Executable: C:\Users\marco\snap_code\GraalPyTest\venv\Scripts\python.exe
	CAPI: 
	JNI library: 
[python::PythonContext] WARNING: could not determine Graal.Python's core path - you may need to pass --python.CoreHome.
[python::PythonContext] WARNING: could not determine Graal.Python's sys prefix path - you may need to pass --python.SysPrefix.
[python::PythonContext] WARNING: could not determine Graal.Python's standard library path. You need to pass --python.StdLibHome if you want to use the standard library.
[python::PythonContext] WARNING: could not determine Graal.Python's C API library path. You need to pass --python.CAPI if you want to use the C extension modules.

I wonder If I should worry about and set the paths explicitly? And which paths are those?

[msimacek]

It's definitely a problem, but you shouldn't set the paths manually, GraalPy should be able to find them. How do you execute GraalPy and how did you create the virtualenv? And what GraalPy version is this?