On Thu, 2017-02-02 at 11:34 -0800, Craig Rodrigues wrote:
> > Which in turn means 'pip3 install Django' actually used the system-
> > wide
> > pip3 command which tried to install Django to the system-wide
> > location
> > and failed.
> >
> >
>
> After you create your Python 3 virtualev, what
Hi!
If I create a Python 2 virtual environment with virtualenv and the --
system-site-packages option, installation of any subsequent package
works as expected:
[vagrant@tadej-zbook ~]$ rpm -q python2-virtualenv
python2-virtualenv-15.0.3-2.fc25.noarch
[vagrant@tadej-zbook ~]$ virtualenv
On Fri, 2017-02-10 at 15:28 +0100, Nick Coghlan wrote:
>
> On 8 February 2017 at 13:44, Tadej Janež <tade...@nez.si> wrote:
> >
> > As I see it, there are two issues when one has the aforementioned
> > three
> > way combination:
> >
> > 1)
On Fri, 2017-02-10 at 09:34 -0500, Donald Stufft wrote:
>
> It’s not a Fedora bug really, it’s a venv bug, virtualenv has special
> logic to
> ensure pip actually gets installed with system site packages and when
> we
> Implemented that in venv I forgot to do it. It looks like it’s
> already been
Hi!
We are a little late with the EuroPython Attendee badge this year, but
nonetheless, it is available and I'm able to award it.
So, if you attended this years EuroPython and would like to have this
badge, just write to me. For more information, see:
Hi,
On Wed, 2019-02-06 at 15:04 +0100, Miro Hrončok wrote:
>
> I've grepped the usage and skimmed trough specs, destining the
> following list of
> packages that fail to properly set both flags.
I've also found that one of my packages was settings CFLAGS to
%{optflags} and fixed it:
On Thu, 2019-02-07 at 00:45 +0100, Miro Hrončok wrote:
> On 06. 02. 19 22:16, Tadej Janež wrote:
> >
> > I've also found that one of my packages was settings CFLAGS to
> > %{optflags} and fixed it:
> > https://src.fedoraproject.org/rpms/bup/c/e960755aa88e1dcf84463faa66c
