[Bug] onecode-check should only check files called by the main, not all present files

[markjessell]

Type

New feature

Product

OneCode Cloud

Details

I have a qgis plugin that I would like to provide as a onecode app whilst keeping the basecode unchanged. To do this I need main.py to ignore a number of libraries (or whole python files) since they cannot be pip installed (qgis specifically).

The .onecodeIgnore file would list the libraries (of files) that the developer knows will not be called by the run() in flows.

Thanks!

[theweaklink]

Hi Mark,

back from holidays, sorry for the late reply. To make sure I understand properly, you mean these libraries and files should be not be imported when executing the main.py

For instance:

# main.py

import qgis.core
import .internal.qgis_stuff
import geopandas as pd

def run():
    # ...

# .onecodeignore
qgis.core
.internal.qgis_stuff

Something like that?

[markjessell]

Hi thanks for considering this. For context I have a qgis plugin where all the calcs are backend and use normal python libraries, and the front end gui and interaction with qgis is confined to two *.py files that will not be used in a onecode context. Therefore if there were a .onecodeIgnore file that could list *.py files to ignore then that would solve the problem for a shared codebase. The alternative would be to ignore specific libraries, but I would prefer just to ignore whole files. thanks

…

________________________________ From: Weaklink ***@***.***> Sent: Wednesday, August 20, 2025 12:48 AM To: deeplime-io/onecode ***@***.***> Cc: Mark Jessell ***@***.***>; Author ***@***.***> Subject: Re: [deeplime-io/onecode] [Request]: .onecodeIgnore file (Issue #45) [https://avatars.githubusercontent.com/u/21156424?s=20&v=4]theweaklink left a comment (deeplime-io/onecode#45)<#45 (comment)> Hi Mark, back from holidays, sorry for the late reply. To make sure I understand properly, you mean these libraries and files should be not be imported when executing the main.py For instance: # main.py import qgis.core import .internal.qgis_stuff import geopandas as pd def run(): # ... # .onecodeignore qgis.core .internal.qgis_stuff Something like that? — Reply to this email directly, view it on GitHub<#45 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABUBSYFHXYVVCWFGCLLO6XD3ONIPNAVCNFSM6AAAAACDJPLJASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMBRGQ4DENBSGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[theweaklink]

Hi @markjessell I think I got what you expected.
When starting the main.py, locally OneCode checks you have all library installed in your current env and display the following output:

2025-08-28 14:57:31,598 [INFO]  - |OneCode|.main.py:65 - Checking required dependencies are in Python environment...
2025-08-28 14:57:31,598 [INFO]  - |OneCode|.main.py:66 - (Use Environment variable ONECODE_FLAG_CHECK_MODULES=0 to turn it off)
2025-08-28 14:57:31,719 [WARNING]  - |OneCode|.main.py:76 - The following libraries may be missing from your Python environment or mismatch the requirements.
2025-08-28 14:57:31,719 [WARNING]  - |OneCode|.main.py:82 - 💥 geoh5py not in Python environment
2025-08-28 14:57:31,719 [WARNING]  - |OneCode|.main.py:82 - 🚫 scipy not in requirements.txt
2025-08-28 14:57:31,719 [WARNING]  - |OneCode|.main.py:82 - 💥 setuptools not in Python environment
2025-08-28 14:57:31,720 [WARNING]  - |OneCode|.main.py:84 - Run 'onecode-require requirements.txt' then 'pip install -r requirements.txt' to try to fix it.

Indeed it should normally check only the import called by the main => instead it calls all the import of any Python file in the directory.

I would therefore classify it as a bug and you shouldn't have to write a .onecodeignore file, it should be taken into account.

In the meantime, to turn these warning off, you can set the env variable ONECODE_FLAG_CHECK_MODULES to 0 like this:

export ONECODE_FLAG_CHECK_MODULES=0
python main.py

or (one-liner)

ONECODE_FLAG_CHECK_MODULES=0 python main.py

Thanks for catching it!

[markjessell]

OK, that is even better (or at least it will be once the bug is fixed) thanks Mark

…

________________________________ From: Weaklink ***@***.***> Sent: Thursday, August 28, 2025 10:53 PM To: deeplime-io/onecode ***@***.***> Cc: Mark Jessell ***@***.***>; Mention ***@***.***> Subject: Re: [deeplime-io/onecode] [Request]: .onecodeIgnore file (Issue #45) [https://avatars.githubusercontent.com/u/21156424?s=20&v=4]theweaklink left a comment (deeplime-io/onecode#45)<#45 (comment)> Hi @markjessell<https://github.com/markjessell> I think I got what you expected. When starting the main.py, locally OneCode checks you have all library installed in your current env and display the following output: 2025-08-28 14:57:31,598 [INFO] - |OneCode|.main.py:65 - Checking required dependencies are in Python environment... 2025-08-28 14:57:31,598 [INFO] - |OneCode|.main.py:66 - (Use Environment variable ONECODE_FLAG_CHECK_MODULES=0 to turn it off) 2025-08-28 14:57:31,719 [WARNING] - |OneCode|.main.py:76 - The following libraries may be missing from your Python environment or mismatch the requirements. 2025-08-28 14:57:31,719 [WARNING] - |OneCode|.main.py:82 - 💥 geoh5py not in Python environment 2025-08-28 14:57:31,719 [WARNING] - |OneCode|.main.py:82 - 🚫 scipy not in requirements.txt 2025-08-28 14:57:31,719 [WARNING] - |OneCode|.main.py:82 - 💥 setuptools not in Python environment 2025-08-28 14:57:31,720 [WARNING] - |OneCode|.main.py:84 - Run 'onecode-require requirements.txt' then 'pip install -r requirements.txt' to try to fix it. Indeed it should normally check only the import called by the main => instead it calls all the import of any Python file in the directory. I would therefore classify it as a bug and you shouldn't have to write a .onecodeignore file, it should be taken into account. In the meantime, to turn these warning off, you can set the env variable ONECODE_FLAG_CHECK_MODULES to 0 like this: export ONECODE_FLAG_CHECK_MODULES=0 python main.py or (one-liner) ONECODE_FLAG_CHECK_MODULES=0 python main.py Thanks for catching it! — Reply to this email directly, view it on GitHub<#45 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABUBSYFUX2UYB7OMJ4FAA2L3P4JVXAVCNFSM6AAAAACDJPLJASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZTHAZDMMJYHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>