-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Bare Git Repo at UNC Shared Drive Filepath #5493
Bare Git Repo at UNC Shared Drive Filepath #5493
Comments
Can you try the fix at #5428? Unsure if it's related to git client usage. |
This one is likely because the project does not define |
You were right. I made a copy of the repo to test with and that messed up the package name. |
The next issue I get is "Invalid git url". This seems to be happening because I am using a hidden folder on Windows. Changing the PATH regex pattern in "poetry\core\vcs\git.py" PATH = r"[\w\~.\-/\\]+" to PATH = r"[\w\$~.\-/\\]+" resolves the issue in addition to using 4 slashes after the schema and : Final filepath looks like: |
@ConnorSMaynes can you try #5428 please? |
Feel free to als osend a PR to core with the regex fix. |
@abn I was going to do a pull request, but I cannot find the source file in the repo. I do not use github that often, so apologies if i am missing the obvious. |
No worries. It is a different project ( |
#5428 also seems to be working, thank you. |
I was using I believe the issue is that the build-system in pyproject still points to the one from pypi and not the dulwich one. I tried the following variations but none worked. [build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api" [build-system]
requires = ["git+https://github.com/abn/poetry@use-dulwich"]
build-backend = "poetry.core.masonry.api" [build-system]
requires = ["poetry@git+https://github.com/abn/poetry@use-dulwich#egg=poetry"]
build-backend = "poetry.core.masonry.api" For the last one I got the following traceback
|
@ConnorSMaynes the As mentioned above, this is a validation done in core. I suspect the issue is, as you pointed out, the use of |
This enables support for dynamically setting the package version (e.g., from a plugin) Resolves: python-poetry/poetry#5493
This enables support for dynamically setting the package version (e.g., from a plugin) Resolves: python-poetry/poetry#5493
This enables support for dynamically setting the package version (e.g., from a plugin) Resolves: python-poetry/poetry#5493
This enables support for dynamically setting the package version (e.g., from a plugin) Resolves: python-poetry/poetry#5493
This enables support for dynamically setting the package version (e.g., from a plugin) Resolves: python-poetry/poetry#5493
This enables support for dynamically setting the package version (e.g., from a plugin) Resolves: python-poetry/poetry#5493
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Issue
System: latest version of poetry, python 3.10.2, Windows 10 64-bit
I have a bare GIT repo on a shared drive which I need to include as a dependency. I have the following dependency in pyproject.toml:
When using "poetry build" I get the following error:
No file/folder found for package
"poetry install" seems to silently fail. It does not install the dependency.
In setuptools setup.py I can use the following path and install/uninstall works without issue:
repo-name@file://drive-name/path/repo-name.git#egg=repo-name
The documentation seems, as far as I can tell, a little sparse on this scenario.
What am I missing?
The text was updated successfully, but these errors were encountered: