> On Mon, Mar 21, 2016 at 05:35:03PM -0400, Neal Gompa wrote:
> Ah, OK. It didn't at some point and I didn't check.
> It seems that the Guidelines:Python page could still use some
> editing. I think most of the info is there, but it's not very clear.
>
> In particular, the multiple-executables cas
- Original Message -
> From: "Zbigniew Jędrzejewski-Szmek"
> To: "Fedora Python SIG"
> Sent: Tuesday, March 22, 2016 2:54:44 AM
> Subject: Re: Inconsistencies in the Fedora Packaging Guidelines for Python
>
> On Mon, Mar 21, 2016 at 05:35:03PM -0
On Mon, Mar 21, 2016 at 05:35:03PM -0400, Neal Gompa wrote:
> On Mon, Mar 21, 2016 at 3:55 PM, Miro Hrončok wrote:
> > On 21.3.2016 20:13, Zbigniew Jędrzejewski-Szmek wrote:
> >>
> >> On Mon, Mar 21, 2016 at 06:46:00PM -, Tomas Orsava wrote:
> >>>
> >>> Since the spec file does package both p2
On Mon, Mar 21, 2016 at 3:55 PM, Miro Hrončok wrote:
> On 21.3.2016 20:13, Zbigniew Jędrzejewski-Szmek wrote:
>>
>> On Mon, Mar 21, 2016 at 06:46:00PM -, Tomas Orsava wrote:
>>>
>>> Since the spec file does package both p2 and p3 versions of the
>>> executable
>>
>>
>> There's a difference bet
On 21.3.2016 20:13, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Mar 21, 2016 at 06:46:00PM -, Tomas Orsava wrote:
Since the spec file does package both p2 and p3 versions of the executable
There's a difference between *modules* (in the Python sense,
i.e. Python libraries) and *executables*.
On Mon, Mar 21, 2016 at 06:46:00PM -, Tomas Orsava wrote:
> Since the spec file does package both p2 and p3 versions of the executable
There's a difference between *modules* (in the Python sense,
i.e. Python libraries) and *executables*. We almost always want
to provide modules for both Python
> But this section explicitly only covers the rare case where a py2 and
> py3 version of something provide _different_ functionality.
> The example spec is for the normal case. That's why it's up above the
> "Avoiding collisions between the python 2 and python 3 stacks" section.
> That section cov
> "TO" == Tomas Orsava writes:
TO> Hi, according to the "Fedora Packaging Guidelines for Python" [0]
TO> the "Example common spec file" [1] contained in those very same
TO> guidelines is wrong.
I think you misunderstand.
TO> Specifically, the section "Naming" [2] in the guidelines says the