-
Notifications
You must be signed in to change notification settings - Fork 156
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 can not be located in a sub-directory of a repository #38
Comments
I face the same issue as well, having a repository of version-synchronized packages. Consider a javascript and a python flask project developed in the same repository etc. Would there be any problems related to removing the version checks? It seems that a git based version number could be used any time |
Is this something that is being looked at? We have the same need. |
I hit the same issue here. Would be a nice improvement. |
Now that 0.15 is out, we should look at fixing this. I'll take a look at #61 and see if I can adapt it to the (large) changes that have landed since then. Thanks! |
Would be great if that went into the next release! I love |
+1 |
Note that current pip-8.1.1 has a bug/issue that causes If you see other problems with subprojects like this, please open a new bug.. I wouldn't be surprised if there are other corner cases that are broken somehow. And if current master seems to work for you, please chime in here; it could definitely use more real-world testing than what I've been able to do locally. |
The versioneer script does not allow the creation of python modules which are sub-directories of a git repository.
ex:
While this directory structure may not be a best practice, it can be a useful construct when building rapid prototypes.
The text was updated successfully, but these errors were encountered: