-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python setup.py develop broken #714
Comments
from
|
@dkeeney could you look at this, please? I've recently struggeled with some py code until I realized I was working on an outdated code. |
PR #747 may fix this. There is a change to setup.py which does a touch of It still requires at least one of the expansion libs to be deleted before it will build. We might want to remove the step that looks for each of the expansion libs before deciding to call CMake. |
Thanks!
if that would not slow down the build process too much, we should do this. The idea of |
Hmmm, I think what is happening is that the develop call is re-packaging the .py code that is already in |
So if this will work, i can call something like 'python develop install --user --force' and pyfiles will be reflected immediately? Since now, i was deleting "distr" folder every time and running 'python install --user --force' |
I think the
develop
mode is broken, as it links tobuild/Release/distr/src
while the changes should be "live" on source files.
Intention of 'develop' py install is that you can make changes to the python files and the package (is linked) will immediately reflect that.
The text was updated successfully, but these errors were encountered: