On Fri, Nov 29, 2019 at 10:42:45AM +, Simon McVittie wrote:
>
> I've opened
> https://salsa.debian.org/cpython-team/python3-defaults/merge_requests/2
> to clarify this. Comments welcome, particularly if you don't think my
> proposed change reflects consensus.
Thanks. This is more clear. I
On Thu, 28 Nov 2019 at 17:27:53 +, Simon McVittie wrote:
> On Thu, 28 Nov 2019 at 11:15:31 -0500, Sandro Tosi wrote:
> > if you install `pubsub` as top-level module, your package must be
> > named pythonN-pubsub, if not it violates the policy and it's RC buggy.
>
> That's what I had thought,
On Fri, 29 Nov 2019 at 08:30:16 +0800, Yao Wei (魏銘廷) wrote:
> The binary package for module foo should preferably be named
> python3-foo, if the module name allows
>
> If the module name has upper case in it, it would actually break Policy §5.6.1
I'd assumed the "foo" here was shorthand
> On Nov 29, 2019, at 01:28, Simon McVittie wrote:
>
> Is there consensus that the top-level module name is what matters, and not
> following the recommendation is a bug?
> https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html
> says "The binary package for module foo
On November 28, 2019 5:27:53 PM UTC, Simon McVittie wrote:
>On Thu, 28 Nov 2019 at 11:15:31 -0500, Sandro Tosi wrote:
>> if you install `pubsub` as top-level module, your package must be
>> named pythonN-pubsub, if not it violates the policy and it's RC
>buggy.
>
>That's what I had thought,
Hi,
čt 28. 11. 2019 v 17:11 odesílatel Andreas Tille napsal:
> Hmmm, what are the chances to get this applied? I've added
>
tbh dunno :)
> in Git - but this will not reall fix the test. The only solution I'd see
> otherwise is to deactivate the test.
>
you have two options:
1. deactivate
On Thu, 28 Nov 2019 at 11:15:31 -0500, Sandro Tosi wrote:
> if you install `pubsub` as top-level module, your package must be
> named pythonN-pubsub, if not it violates the policy and it's RC buggy.
That's what I had thought, but I've also seen people asserting that the
Debian package name ought
On Thu, Nov 28, 2019 at 11:15:31AM -0500, Sandro Tosi wrote:
> > Hmmm, what are the chances to get this applied? I've added
> >
> >X-Python-Module-Name: pubsub
> >
> > in Git - but this will not reall fix the test. The only solution I'd see
> > otherwise is to deactivate the test.
>
> if
On Thu, Nov 28, 2019 at 11:11 AM Andreas Tille wrote:
>
> On Thu, Nov 28, 2019 at 04:18:07PM +0100, Ondrej Novy wrote:
> >
> > > Is there any trick to enable autopkgtest-pkg-python detecting the correct
> > > module name?
> > >
> >
> > no (not yet? See:
On Thu, Nov 28, 2019 at 04:18:07PM +0100, Ondrej Novy wrote:
>
> > Is there any trick to enable autopkgtest-pkg-python detecting the correct
> > module name?
> >
>
> no (not yet? See: https://salsa.debian.org/ci-team/autodep8/merge_requests/6
> )
Hmmm, what are the chances to get this applied?
Hi,
čt 28. 11. 2019 v 16:04 odesílatel Andreas Tille napsal:
> Is there any trick to enable autopkgtest-pkg-python detecting the correct
> module name?
>
no (not yet? See: https://salsa.debian.org/ci-team/autodep8/merge_requests/6
)
--
Best regards
Ondřej Nový
11 matches
Mail list logo
