-
Notifications
You must be signed in to change notification settings - Fork 49
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
Errors encountered installing git-deps under Windows #92
Comments
i get the same error |
Hi, I've just released 1.1.0. Any chance you could test whether you still see this issue? Thanks! |
Hi, I am getting the error in version 1.1.0. C:\Users\xyz>pip3 install git-deps
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. |
Thanks for the confirmation. I have no clue how to fix that, and TBH it doesn't sound like it's related to git-deps, but I will leave the issue open anyway. Perhaps you could try upgrading pip or even Python? |
@aspiers can I assume you are not attempting this on Windows? It seems Python has different behavior under Windows than other platforms, in that "open()" does not default to utf-8. There might be a bug somewhere in the package deployment stack (not necessarily in git-deps) with an open() call that doesn't specify utf-8-sig as the default encoding, and that runs into problems with certain content (which might be in git-deps). |
That's correct, I use Linux. I will have to rely on Windows users to help debug this. Yes, that sounds like a very reasonable possibility. |
I'm not able to run "pip install git-deps" under Windows 10.
error in setup command: Error parsing C:\Users\johndog\AppData\Local\Temp\2\pip-install-_m6ma4lh\git-deps\setup.cfg: UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 910: character maps to <undefined>
I ran pip with --no-clean and looked at the setup.cfg, but I didn't see any problems in it (or even a byte 0x9d), so it must be somewhere else than implied by the error message.
The text was updated successfully, but these errors were encountered: