Re: Critical problem in PyCharm caused by the removal of "--build-dir" in 2020.3

Bernat Gabor <[email protected]> Mon, 30 Nov 2020 18:51:53 +0000
Newsgroups gmane.comp.python.distutils.devel
Message-ID <CALBzji6yF2Lt7MKzK+-n=8sm43VTPF2Sa=x=XKiYBirgtahpgg@mail.gmail.com>
--===============5496210155725391938==
Content-Type: multipart/alternative; boundary="000000000000a0388805b5578155"

--000000000000a0388805b5578155
Content-Type: text/plain; charset="UTF-8"

Hello,

You want to raise the issue directly at the pip issue tracker,
https://github.com/pypa/pip. This mailing list is reserved mostly for
general packaging related topics.

Thanks,

On Mon, Nov 30, 2020 at 6:47 PM Mikhail Golubev via Distutils-SIG <
[email protected]> wrote:

> Hi there!
>
> I'm a member of the PyCharm team, and we faced a rather critical issue
> with the release of pip 2020.3 (
> https://youtrack.jetbrains.com/issue/PY-45712). It turned out that we
> actually still used the "--build-dir" option in our internal scripts for
> installing packages through pip, and we completely missed the fact that it
> was deprecated. To make the matter worse, a few releases back we
> implemented automatic upgrading of packaging tools in all virtual
> environments created in the IDE, so now it's impossible to install anything
> in a new project unless pip is explicitly downgraded first.
>
> Judging by how pip now operates regarding building of packages, this
> option can be safely dropped in our wrappers, but we still need some time
> to prepare and test patches for a few previous releases and upcoming
> 2020.3. Is it possible to give us some time to soften the blow for the
> users?
>
> The second question is about the behavior of this option. It appears that
> we initially started using it because in the past packages were not built
> in a temporary directory by default. Could you please point me to the exact
> version of pip where it changed? -- I couldn't find it in a changelog. It
> would help us decide whether we need to keep some compatibility layer for
> interpreters with an old version of pip installed.
>
> Thanks a lot!
> --
> Distutils-SIG mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/distutils-sig.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/6Z5DQGRDGOU4OCO3JSS4FVYWV5JBUPVP/
>

--000000000000a0388805b5578155
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<br><br>You want to raise the issue directly at the =
pip issue tracker,=C2=A0<a href=3D"https://github.com/pypa/pip">https://git=
hub.com/pypa/pip</a>. This mailing list is reserved mostly for general pack=
aging related topics.<br><br>Thanks,</div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 30, 2020 at 6:47 PM Mikhail=
 Golubev via Distutils-SIG &lt;<a href=3D"mailto:[email protected]">=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Hi there!<br>
<br>
I&#39;m a member of the PyCharm team, and we faced a rather critical issue =
with the release of pip 2020.3 (<a href=3D"https://youtrack.jetbrains.com/i=
ssue/PY-45712" rel=3D"noreferrer" target=3D"_blank">https://youtrack.jetbra=
ins.com/issue/PY-45712</a>). It turned out that we actually still used the =
&quot;--build-dir&quot; option in our internal scripts for installing packa=
ges through pip, and we completely missed the fact that it was deprecated. =
To make the matter worse, a few releases back we implemented automatic upgr=
ading of packaging tools in all virtual environments created in the IDE, so=
 now it&#39;s impossible to install anything in a new project unless pip is=
 explicitly downgraded first.<br>
<br>
Judging by how pip now operates regarding building of packages, this option=
 can be safely dropped in our wrappers, but we still need some time to prep=
are and test patches for a few previous releases and upcoming 2020.3. Is it=
 possible to give us some time to soften the blow for the users?<br>
<br>
The second question is about the behavior of this option. It appears that w=
e initially started using it because in the past packages were not built in=
 a temporary directory by default. Could you please point me to the exact v=
ersion of pip where it changed? -- I couldn&#39;t find it in a changelog. I=
t would help us decide whether we need to keep some compatibility layer for=
 interpreters with an old version of pip installed.<br>
<br>
Thanks a lot!<br>
--<br>
Distutils-SIG mailing list -- <a href=3D"mailto:[email protected]" t=
arget=3D"_blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:distutils-sig-leave@pytho=
n.org" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://mail.python.org/mailman3/lists/distutils-sig.python.org/=
" rel=3D"noreferrer" target=3D"_blank">https://mail.python.org/mailman3/lis=
ts/distutils-sig.python.org/</a><br>
Message archived at <a href=3D"https://mail.python.org/archives/list/distut=
[email protected]/message/6Z5DQGRDGOU4OCO3JSS4FVYWV5JBUPVP/" rel=3D"norefe=
rrer" target=3D"_blank">https://mail.python.org/archives/list/distutils-sig=
@python.org/message/6Z5DQGRDGOU4OCO3JSS4FVYWV5JBUPVP/</a><br>
</blockquote></div>

--000000000000a0388805b5578155--

--===============5496210155725391938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Distutils-SIG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/archives/list/[email protected]/message/MX6RBICVYCZMSNNWUXKW2CQQX7WI5L57/

--===============5496210155725391938==--