question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Git and Mercurial revision checkout not working under Windows

See original GitHub issue

The revision checkout routines located in setuptools/setuptools/package_index.py, functions _download_git and _download_hg, rely on (cd %s && <command>) to execute <command> in %s. This does not work under Windows, as simply tested by executing cd .. && echo %cd%.

Further reading: https://stackoverflow.com/q/55641332

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
benoit-pierrecommented, Apr 13, 2019

@jaraco: well, using git -C is cleaner, although the code still suffer from some of the same issues (no escaping of arguments for example). I don’t think there’s a point in spending more time investigating the issue when most of this code is deprecated by the use of pip.

@2xB: the unfortunate truth is direct URL requirements are a very poor replacement for dependency links. In fact, I think there’s pretty much useless, see discussion here: https://github.com/pypa/pip/issues/5898.

In your case, I would change the requirement to pyqtgraph==0.11.0.dev0+g7201bae, forget about dependency links or using a direct URL requirement, and then either maintain a custom index if your creating private packages or make the wheel / source distribution available at a public URL so you can ask users to install using pip install -f public_url_for_patched_pyqtgraph_version mypackage. There’s no way to get pip to install the custom version with a simple pip install mypackage invocation.

1reaction
jaracocommented, Apr 12, 2019

I hadn’t read this thread before accepting the PR (I probably should have). I do think the proposed approach is more robust than the one that was used previously, so I’m happy to see it incorporated, even if it is using behavior in discouraged parts of the codebase.

I did not intend to countermand Benoit’s opinion. Happy to revert at your discretion, @benoit-pierre.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Mercurial go back n revisions before the current one
In mercurial how can I go back n revisions from the revision I'm currently on? This answer shows how it can be done...
Read more >
Code Repository Troubleshooting - Visual Studio App Center
Troubleshooting issues with code repositories in Build.
Read more >
GitConcepts - Mercurial
In Git you need a configuration option for that, whereas in Hg you only need to check out the null revision, like this:...
Read more >
Version Control: Git, Mercurial - Hyperpolyglot
git hg show version $ git version $ hg version get help for subcommand $ git help CMD $ hg help CMD list topic guides $...
Read more >
Mercurial command cheat sheet - gists · GitHub
Mercurial command cheat sheet. GitHub Gist: instantly share code, notes, and snippets.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found