From: ankostis <ankostis@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Adam Dinwoodie <adam@dinwoodie.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
cygwin@cygwin.com
Subject: Re: CYGWIN git cannot install python packages with pip
Date: Tue, 16 May 2017 15:09:36 +0200 [thread overview]
Message-ID: <CA+dhYEVW1ozj17DT0Asz4iuLXQpCpEckOOqVBe2baLhmzmEopA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705041324030.4905@virtualbox>
On 4 May 2017 at 13:26, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Thu, 4 May 2017, ankostis wrote:
>
>> On 4 May 2017 at 11:47, Adam Dinwoodie <adam@dinwoodie.org> wrote:
>> Judging from the error-message, it somehow concatenates input & output
>> paths.
>> Isn't this something to research about?
>
> It is something to research about. But by you, not by me.
You got a point there.
> I need to focus
> on bigger-impact issues, because I do not scale, and Git for Windows'
> users generally do not experience the problem you described.
Git for Windows uses MINGW indeed.
But there are still CYGWIN users out in the wild
running the vanilla Windows python installation.
Actually this issue has a big impact on those of us because
recent `setuptools` tools allow for packages to specify project dependencies
using the `git+https://...` url-scheme.
So the problem may appear to unaware users just trying to install
a packages the regular way, with `pip install foo.package`
Great thanks,
Kostis
FYI, cross-posting also to CYGWIN list.
next prev parent reply other threads:[~2017-05-16 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 18:08 CYGWIN git cannot install python packages with pip ankostis
2017-05-02 18:40 ` ankostis
2017-05-03 9:47 ` Johannes Schindelin
2017-05-03 10:21 ` ankostis
2017-05-03 14:32 ` Johannes Schindelin
2017-05-04 9:47 ` Adam Dinwoodie
2017-05-04 10:18 ` ankostis
2017-05-04 11:26 ` Johannes Schindelin
2017-05-16 13:09 ` ankostis [this message]
2017-05-16 13:15 ` ankostis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+dhYEVW1ozj17DT0Asz4iuLXQpCpEckOOqVBe2baLhmzmEopA@mail.gmail.com \
--to=ankostis@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).