On Thu, Dec 04, 2014 at 12:51:40AM +1000, Nick Coghlan wrote:
>
> On 4 Dec 2014 00:38, "Bohuslav Kabrda" wrote:
> >
> > So here are my proposals for changes in current guidelines [2]:
> > - In [3], it says "If the executables provide the same functionality
> independent of whether they are run on
- Original Message -
> On Dec 3, 2014, at 9:51 AM, Nick Coghlan < ncogh...@gmail.com > wrote:
> > > - (This is not really related to the switch, but more of a general
> > > remark)
> > > In [4], it says that "python 3 version of the executable gains a python3-
> > > prefix". This is IMO b
On 4 Dec 2014 00:59, "Donald Stufft" wrote:
>
>
> On Dec 3, 2014, at 9:51 AM, Nick Coghlan wrote:
>
>> > - (This is not really related to the switch, but more of a general
remark) In [4], it says that "python 3 version of the executable gains a
python3- prefix". This is IMO bad, since upstream pr
> On Dec 3, 2014, at 9:51 AM, Nick Coghlan wrote:
>
> > - (This is not really related to the switch, but more of a general remark)
> > In [4], it says that "python 3 version of the executable gains a python3-
> > prefix". This is IMO bad, since upstream projects tend to name the
> > versioned
On 4 Dec 2014 00:38, "Bohuslav Kabrda" wrote:
>
> So here are my proposals for changes in current guidelines [2]:
> - In [3], it says "If the executables provide the same functionality
independent of whether they are run on top of Python 2 or Python 3, then
only one version of the executable shoul
Hi all,
as you are well aware, there is the "Python 3 as Default" change proposed for
F22 [1]. There are several guideline changes that will need to be done and some
that may be done in order to improve the situation. I'd like to make this
thread a sort of brainstorming on my thoughts as well as
