fix: revert to setting PYTHONPATH on the composefile for dev

[sergiolaverde0]

This commit reverts the process of setting the PYTHONPATH on the dev environment to being done on the composefile instead of doing it during the build process.

[simjanos-dev]

Thank you!

Can you please explain 2 things:

• What is the difference between creating the env variable in the dockerfile and the docker compose yml file, what caused the problem?
• If I understand it correctly, this overwrites the PYTHONPATH, which tells python where to look for packages. Does python have some default paths, that you cannot remove, and this is the reason it looks both in the models folder and in the default python install folder?

[sergiolaverde0]

• I'm assuming that the issue is trying to set the variable to some location that doesn't exist yet, so moving it to the creation of the container ensures it is correctly set to the mounted folder. Or at least that's my hypothesis, I'm not really certain.
• By default that variable should be unset and setting it only adds extra places for Python to look for packages on top the already defined in PYTHONHOME and the library locations according to the documentation.

If this doesn't work yet I have thought of setting the variable directly inside the script itself, so let me know if any issue arises no matter how small.

[simjanos-dev]

I'm assuming that the issue is trying to set the variable to some location that doesn't exist yet, so moving it to the creation of the container ensures it is correctly set to the mounted folder. Or at least that's my hypothesis, I'm not really certain.

That does make sense. But then why would deleting the storage/app/model directory fix this issue?

If this doesn't work yet I have thought of setting the variable directly inside the script itself, so let me know if any issue arises no matter how small.

I might need a few days to test this again.