> > We discussed the future fate of the /usr/bin/python symlink at the
> > language summit (and a little further at the sprints), and it
> > currently seems likely that we're going to go down the path of the
> > Python Launcher for Windows model, and make "python" refer to a
> > configurable shim t
- Original Message -
> From: "Bohuslav Kabrda"
> To: "Fedora Python SIG"
> Sent: Monday, April 20, 2015 9:02:35 AM
> Subject: Re: Python3 as default
>
> - Original Message -
> > +1 from me on the suggested changes.
> >
> > On 15 April 2015 at 02:56, Robert Kuska wrote:
> > >
(I've miss hitted enter and sent the email earlier)
- Original Message -
> From: "Robert Kuska"
> To: "Fedora Python SIG"
> Sent: Monday, April 20, 2015 10:05:44 AM
> Subject: Re: Python3 as default
>
>
>
> - Original Message -
> > From: "Toshio Kuratomi"
> > To: "Fedora Pyth
- Original Message -
> From: "Toshio Kuratomi"
> To: "Fedora Python SIG"
> Sent: Friday, April 17, 2015 2:14:20 PM
> Subject: Re: Python3 as default
>
>
>
>
> On Apr 15, 2015 2:57 AM, "Robert Kuska" < rku...@redhat.com > wrote:
>
>
> > pip is not a application, even though it is n
- Original Message -
> From: "Nick Coghlan"
> To: "Fedora Python SIG"
> Sent: Friday, April 17, 2015 7:50:54 AM
> Subject: Re: Python3 as default
>
> +1 from me on the suggested changes.
>
> On 15 April 2015 at 02:56, Robert Kuska wrote:
> >
> > *{__python} VS /usr/bin/python CONFUSI
- Original Message -
> +1 from me on the suggested changes.
>
> On 15 April 2015 at 02:56, Robert Kuska wrote:
> >
> > *{__python} VS /usr/bin/python CONFUSION*
> > Why is value of {__python} being changed and /usr/bin/python (along with
> > python-foo being python2)
> > is untached? I se
