-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
file:// protocol not available #2732
Comments
Thanks for this issue! The reason we don't support the I believe there is a pluggable Transport Adapter for the file protocol floating around. You can also consider adapting one from this answer. |
Before opening issues, please search all issues (not just open ones) for similar issues. This is just the earliest issue I could find and there are several others (including pull requests). |
The import-goal --project-list option currently only supports URLs but the requests library doesn't support the file:// protocol: psf/requests#2732 This change adds the ability to read a file path for --project-list instead of rely on URL in case you have a locally modified projects.yaml. Change-Id: I584534fb32f42e5d78941637285623ad96cf79c3 Story: 2003653 Task: 26066
Hello all, and first of all thanks for this awesome library.
While working with requests I was surprised to find out that it doesn't handle the file:// protocol. Even though I understand it's maybe not a key feature of this library it would come in handy for compatibility reasons.
Concretely I have sort of a 'Fetcher' class that servers files from a 'Repository', but this repository can be local or remote. In case of being local I tried (unsuccessfully, of course) to use the file:// protocol. Finally it forced me to considerably increase the number of lines of code I needed to handle the issue.
For example, something like this would be fine:
So far it raises this exception:
My questions are:
The text was updated successfully, but these errors were encountered: