Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #13260 > unrolled thread

How can I override module name in autopkgtest-pkg-python

Started byAndreas Tille <andreas@an3as.eu>
First post2021-03-03 21:20 +0100
Last post2021-03-04 03:00 +0100
Articles 5 — 4 participants

Back to article view | Back to linux.debian.maint.python


Contents

  How can I override module name in autopkgtest-pkg-python Andreas Tille <andreas@an3as.eu> - 2021-03-03 21:20 +0100
    Re: How can I override module name in autopkgtest-pkg-python Gregor Riepl <onitake@gmail.com> - 2021-03-03 21:50 +0100
      Re: How can I override module name in autopkgtest-pkg-python Emmanuel Arias <eamanu@yaerobi.com> - 2021-03-03 23:20 +0100
        Re: How can I override module name in autopkgtest-pkg-python Emmanuel Arias <eamanu@yaerobi.com> - 2021-03-03 23:30 +0100
    Re: How can I override module name in autopkgtest-pkg-python Paul Wise <pabs@debian.org> - 2021-03-04 03:00 +0100

#13260 — How can I override module name in autopkgtest-pkg-python

FromAndreas Tille <andreas@an3as.eu>
Date2021-03-03 21:20 +0100
SubjectHow can I override module name in autopkgtest-pkg-python
Message-ID<BOG8q-57b-11@gated-at.bofh.it>
Hi,

I worked on the package python-cython-blis[1] (there is no specific
reason to have it in Debian Science scope - I just found an existing
repository there and continued with this).

The package works nicely - but the autopkgtest (in Salsa CI[2] does
not):

autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done
autopkgtest [19:46:36]: test autodep8-python3: [-----------------------
Testing with python3.9:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'cython_blis'
autopkgtest [19:46:37]: test autodep8-python3: -----------------------]


The actual module that needs to be importet is just blis.  How can
I teach autodep8-python3 the correct module name?

Kind regards

      Andreas.


[1] https://salsa.debian.org/science-team/python-cython-blis
[2] https://salsa.debian.org/science-team/python-cython-blis/-/jobs/1483087

-- 
http://fam-tille.de

[toc] | [next] | [standalone]


#13262

FromGregor Riepl <onitake@gmail.com>
Date2021-03-03 21:50 +0100
Message-ID<BOGBr-5hf-3@gated-at.bofh.it>
In reply to#13260
> autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done
> autopkgtest [19:46:36]: test autodep8-python3: [-----------------------
> Testing with python3.9:
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
> ModuleNotFoundError: No module named 'cython_blis'
> autopkgtest [19:46:37]: test autodep8-python3: -----------------------]
> 
> 
> The actual module that needs to be importet is just blis.  How can
> I teach autodep8-python3 the correct module name?

Simply write a suitable debian/tests/control file that uses

import blis; print(blis)

instead of

import cython_blis; print(cython_blis)

See here for an example:
https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control

Although, it looks like this sort of trivial autopkgtest is now
considered "superficial" and will no longer reduce the time until a
package is autopromoted to testing.

[toc] | [prev] | [next] | [standalone]


#13264

FromEmmanuel Arias <eamanu@yaerobi.com>
Date2021-03-03 23:20 +0100
Message-ID<BOI0x-6m1-1@gated-at.bofh.it>
In reply to#13262

[Multipart message — attachments visible in raw view] — view raw

Hi,

Maybe this can be useful [0] but that is deprecated. You can create
debian/tests/autopkgtest-pkg-python.conf file and use import_name
variable to change the name. Here an example [1]


[0] https://salsa.debian.org/ci-team/autodep8/-/merge_requests/17
[1]
https://salsa.debian.org/python-team/packages/python-xlib/-/blob/master/debian/tests/autopkgtest-pkg-python.conf

Cheers,
Emmanuel

On Wed, Mar 3, 2021 at 5:49 PM Gregor Riepl <onitake@gmail.com> wrote:

> > autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in
> $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
> with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done
> > autopkgtest [19:46:36]: test autodep8-python3: [-----------------------
> > Testing with python3.9:
> > Traceback (most recent call last):
> >   File "<string>", line 1, in <module>
> > ModuleNotFoundError: No module named 'cython_blis'
> > autopkgtest [19:46:37]: test autodep8-python3: -----------------------]
> >
> >
> > The actual module that needs to be importet is just blis.  How can
> > I teach autodep8-python3 the correct module name?
>
> Simply write a suitable debian/tests/control file that uses
>
> import blis; print(blis)
>
> instead of
>
> import cython_blis; print(cython_blis)
>
> See here for an example:
>
> https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control
>
> Although, it looks like this sort of trivial autopkgtest is now
> considered "superficial" and will no longer reduce the time until a
> package is autopromoted to testing.
>
>

[toc] | [prev] | [next] | [standalone]


#13265

FromEmmanuel Arias <eamanu@yaerobi.com>
Date2021-03-03 23:30 +0100
Message-ID<BOIad-6pc-1@gated-at.bofh.it>
In reply to#13264

[Multipart message — attachments visible in raw view] — view raw

I note that my last mail can be confuse

The use of debian/tests/pkg-python/import-name is deprecated.

But the use of debian/tests/autopkgtest-pkg-python.conf is
mentioned on man autodep8. So this can be used.

On Wed, Mar 3, 2021 at 7:15 PM Emmanuel Arias <eamanu@yaerobi.com> wrote:

> Hi,
>
> Maybe this can be useful [0] but that is deprecated. You can create
> debian/tests/autopkgtest-pkg-python.conf file and use import_name
> variable to change the name. Here an example [1]
>
>
> [0] https://salsa.debian.org/ci-team/autodep8/-/merge_requests/17
> [1]
> https://salsa.debian.org/python-team/packages/python-xlib/-/blob/master/debian/tests/autopkgtest-pkg-python.conf
>
> Cheers,
> Emmanuel
>
> On Wed, Mar 3, 2021 at 5:49 PM Gregor Riepl <onitake@gmail.com> wrote:
>
>> > autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in
>> $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
>> with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done
>> > autopkgtest [19:46:36]: test autodep8-python3: [-----------------------
>> > Testing with python3.9:
>> > Traceback (most recent call last):
>> >   File "<string>", line 1, in <module>
>> > ModuleNotFoundError: No module named 'cython_blis'
>> > autopkgtest [19:46:37]: test autodep8-python3: -----------------------]
>> >
>> >
>> > The actual module that needs to be importet is just blis.  How can
>> > I teach autodep8-python3 the correct module name?
>>
>> Simply write a suitable debian/tests/control file that uses
>>
>> import blis; print(blis)
>>
>> instead of
>>
>> import cython_blis; print(cython_blis)
>>
>> See here for an example:
>>
>> https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control
>>
>> Although, it looks like this sort of trivial autopkgtest is now
>> considered "superficial" and will no longer reduce the time until a
>> package is autopromoted to testing.
>>
>>

[toc] | [prev] | [next] | [standalone]


#13266

FromPaul Wise <pabs@debian.org>
Date2021-03-04 03:00 +0100
Message-ID<BOLrr-8pW-1@gated-at.bofh.it>
In reply to#13260
On Wed, Mar 3, 2021 at 8:12 PM Andreas Tille wrote:

> I worked on the package python-cython-blis[1]

FYI, upstream is very hostile towards having their software in Debian
so I suggest you cease packaging this and anything that depends on it:

https://github.com/explosion/cython-blis/issues/32

The developers reference mentions that packaging software with hostile
upstream developers is often not a good idea.

https://www.debian.org/doc/manuals/developers-reference/developer-duties.en.html#coordination-with-upstream-developers

"If you find that the upstream developers are or become hostile
towards Debian or the free software community, you may want to
re-consider the need to include the software in Debian. Sometimes the
social cost to the Debian community is not worth the benefits the
software may bring."

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web