search

scientific-python / lazy-loader

Populate library namespace without incurring immediate import costs
BSD 3-Clause "New" or "Revised" License
116 stars 19 forks source link

Problem on running "production" #86

Closed TomFreudenberg closed 3 months ago

TomFreudenberg commented 5 months ago

Hi, thanks for this project and your effort.

Using it on the boilerplate Cedra I could manage to integrate dramatiq into a Cement app.

But running built project "in production" does not seem to work.

When I setup the project after checkout by:

python setup.py install

The lazy-loader doesn't seems to do it's job.

Running the same by using

python setup.py develop

all ist working fine.

You can test it with the above project, after checkout (inside project folder):

rm -rf .venv ; make virtualenv ; source .venv/bin/activate ; python setup.py install ; cedra --help

does not work

but instead 

rm -rf .venv ; make virtualenv ; source .venv/bin/activate ; python setup.py develop ; cedra --help

does work.

Any suggestions?

Cheers Tom

stefanv commented 5 months ago

Hi @TomFreudenberg, we'd need a bit more information to debug here. What do you mean by "does not work"?

Note that setup.py develop is nowadays spelled pip install --no-build-isolation -e ., and python setup.py install becomes pip install ..

stefanv commented 3 months ago

Closing due to lack of information.