> unversioned executable
> > > `example` will be packaged under `python2-example` (hence running on
> python2).
>
> Yes, this is a very nice description. It would be great this become
> part of the guidelines, because this is an issue that comes up quite
> often. Current gu
t; executable
> > `example` will be packaged under `python2-example` (hence running on
> > python2).
Yes, this is a very nice description. It would be great this become
part of the guidelines, because this is an issue that comes up quite
often. Current guidelines talk about case 3. pro
gt;
>> Sent: Thursday, January 21, 2016 12:40:47 PM
>> Subject: Re: Python naming guidelines clarification
>>
>> On Wed, Jan 20, 2016 at 11:54 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> > Yes, the guidelines apply to the source rpm name too. Those
>> > srpms
- Original Message -
> From: "Jan Včelák"
> To: "Development discussions related to Fedora"
>
> Sent: Thursday, January 21, 2016 12:40:47 PM
> Subject: Re: Python naming guidelines clarification
>
> On Wed, Jan 20, 2016 at 11:54 PM, Zbigni
On Thu, Jan 21, 2016 at 9:09 AM, Robert Kuska wrote:
> I don't see an use case for python2 subpackage, or am I missing something?
This is a good catch. I'll verify this with upstream. But most
probably, you are right. Thank you.
Jan
--
devel mailing list
devel@lists.fedoraproject.org
http://lists
On Wed, Jan 20, 2016 at 11:54 PM, Zbigniew Jędrzejewski-Szmek wrote:
> Yes, the guidelines apply to the source rpm name too. Those
> srpms should be called python-*, because they contain python libries.
OK. Thank you.
And what is the best current practice if the library contains some
utilities. S
- Original Message -
> From: "Zbigniew Jędrzejewski-Szmek"
> To: "Development discussions related to Fedora"
>
> Sent: Wednesday, January 20, 2016 11:54:30 PM
> Subject: Re: Python naming guidelines clarification
>
> On Wed, Jan 20, 2016 at 09:4
On Wed, Jan 20, 2016 at 09:44:50PM +0100, Jan Včelák wrote:
> Hello.
>
> I've got several Python packages on review. But I'm not sure if the
> naming policy applies to the spec file the same way as it applies on
> the resulting packages.
>
> socketIO-client RHBZ #1300092
> ripe-atlas-sagan RHBZ #
Hello.
I've got several Python packages on review. But I'm not sure if the
naming policy applies to the spec file the same way as it applies on
the resulting packages.
socketIO-client RHBZ #1300092
ripe-atlas-sagan RHBZ #1300217
ripe-atlas-cousteau RHBZ #1300219
ripe-atlas-tools RHBZ #1300222
Fo
