Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10039 > unrolled thread
| Started by | Andreas Tille <andreas@an3as.eu> |
|---|---|
| First post | 2018-01-12 17:10 +0100 |
| Last post | 2018-01-26 17:10 +0100 |
| Articles | 20 — 8 participants |
Back to article view | Back to linux.debian.maint.python
Packaging python-aws-xray-sdk to fullfil a dependency for python-moto Andreas Tille <andreas@an3as.eu> - 2018-01-12 17:10 +0100
If there is no response in debian-python then debian-science might be the right team (Was: Packaging python-aws-xray-sdk to fullfil a dependency for python-moto) Andreas Tille <andreas@an3as.eu> - 2018-01-15 09:40 +0100
Re: If there is no response in debian-python then debian-science might be the right team (Was: Packaging python-aws-xray-sdk to fullfil a dependency for python-moto) Yaroslav Halchenko <yoh@onerussian.com> - 2018-01-15 11:50 +0100
Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Andreas Tille <andreas@an3as.eu> - 2018-01-15 13:00 +0100
Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Simon McVittie <smcv@debian.org> - 2018-01-15 13:30 +0100
Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Andreas Tille <andreas@an3as.eu> - 2018-01-15 13:50 +0100
Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Tristan Seligmann <mithrandi@mithrandi.net> - 2018-01-15 13:30 +0100
Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Piotr Ożarowski <piotr@debian.org> - 2018-01-15 14:00 +0100
Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Andreas Tille <andreas@an3as.eu> - 2018-01-15 16:10 +0100
Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) Piotr Ożarowski <piotr@debian.org> - 2018-01-15 16:20 +0100
Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random' Andreas Tille <andreas@an3as.eu> - 2018-01-16 21:50 +0100
Re: Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random' Tristan Seligmann <mithrandi@mithrandi.net> - 2018-01-17 08:20 +0100
Re: Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random' Andreas Tille <andreas@an3as.eu> - 2018-01-17 11:20 +0100
Bug#777089: Preconditions for python-moto finished - help needed to build package itself Andreas Tille <andreas@fam-tille.de> - 2018-02-02 09:30 +0100
Bug#777089: Preconditions for python-moto finished - help needed to build package itself Olivier Sallou <olivier.sallou@irisa.fr> - 2018-02-02 10:20 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Andreas Tille <andreas@an3as.eu> - 2018-01-22 15:10 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Piotr Ożarowski <piotr@debian.org> - 2018-01-22 15:30 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Olivier Sallou <olivier.sallou@irisa.fr> - 2018-01-23 17:20 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Olivier Sallou <olivier.sallou@irisa.fr> - 2018-01-26 16:20 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Sandro Tosi <morph@debian.org> - 2018-01-26 17:10 +0100
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-12 17:10 +0100 |
| Subject | Packaging python-aws-xray-sdk to fullfil a dependency for python-moto |
| Message-ID | <v7a41-1Y3-1@gated-at.bofh.it> |
Hi,
the Debian Science team needs to update python-pandas sooner or later
and the new version of pandas needs python-moto. I had a look into this
and realised it needs python-aws-xray-sdk[1]. I've created a local Git
packaging repository which I would like to push to salsa.debian.org since
I'm stumbling about issues I need some help for.
I think Debian Python team would be a good team for this package since
it is not really science related. Is this OK to push the package into
Debian Python team repository? If yes did you start the migration to
salsa.debian.org? Otherwise I could push it to alioth but may be its
better if not so many projects end up there once the migration will be
done.
Kind regards
Andreas.
[1] https://github.com/aws/aws-xray-sdk-python
--
http://fam-tille.de
[toc] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-15 09:40 +0100 |
| Subject | If there is no response in debian-python then debian-science might be the right team (Was: Packaging python-aws-xray-sdk to fullfil a dependency for python-moto) |
| Message-ID | <v88tb-7qP-5@gated-at.bofh.it> |
| In reply to | #10039 |
Hi again,
is it correct to assume that Debian Python Modules Team do not want to
see this precondition for a scientific oriented package in its scope and
I should move it to Debian Science?
Kind regards
Andreas.
On Fri, Jan 12, 2018 at 05:01:53PM +0100, Andreas Tille wrote:
> Hi,
>
> the Debian Science team needs to update python-pandas sooner or later
> and the new version of pandas needs python-moto. I had a look into this
> and realised it needs python-aws-xray-sdk[1]. I've created a local Git
> packaging repository which I would like to push to salsa.debian.org since
> I'm stumbling about issues I need some help for.
>
> I think Debian Python team would be a good team for this package since
> it is not really science related. Is this OK to push the package into
> Debian Python team repository? If yes did you start the migration to
> salsa.debian.org? Otherwise I could push it to alioth but may be its
> better if not so many projects end up there once the migration will be
> done.
>
> Kind regards
>
> Andreas.
>
> [1] https://github.com/aws/aws-xray-sdk-python
>
> --
> http://fam-tille.de
>
>
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Yaroslav Halchenko <yoh@onerussian.com> |
|---|---|
| Date | 2018-01-15 11:50 +0100 |
| Subject | Re: If there is no response in debian-python then debian-science might be the right team (Was: Packaging python-aws-xray-sdk to fullfil a dependency for python-moto) |
| Message-ID | <v8alk-eV-7@gated-at.bofh.it> |
| In reply to | #10050 |
I don't mind helping to maintain it under any of those teams. Thank you Andreas for taking care about this new dependency. I will look into updating pandas package On January 15, 2018 3:37:53 AM EST, Andreas Tille <andreas@an3as.eu> wrote: >Hi again, > >is it correct to assume that Debian Python Modules Team do not want to >see this precondition for a scientific oriented package in its scope >and >I should move it to Debian Science? > >Kind regards > > Andreas. > >On Fri, Jan 12, 2018 at 05:01:53PM +0100, Andreas Tille wrote: >> Hi, >> >> the Debian Science team needs to update python-pandas sooner or later >> and the new version of pandas needs python-moto. I had a look into >this >> and realised it needs python-aws-xray-sdk[1]. I've created a local >Git >> packaging repository which I would like to push to salsa.debian.org >since >> I'm stumbling about issues I need some help for. >> >> I think Debian Python team would be a good team for this package >since >> it is not really science related. Is this OK to push the package >into >> Debian Python team repository? If yes did you start the migration to >> salsa.debian.org? Otherwise I could push it to alioth but may be its >> better if not so many projects end up there once the migration will >be >> done. >> >> Kind regards >> >> Andreas. >> >> [1] https://github.com/aws/aws-xray-sdk-python >> >> -- >> http://fam-tille.de >> >> -- Sent from a phone which beats iPhone.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-15 13:00 +0100 |
| Subject | Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8bAJ-11k-7@gated-at.bofh.it> |
| In reply to | #10052 |
Hi Yaroslav,
On Mon, Jan 15, 2018 at 05:26:28AM -0500, Yaroslav Halchenko wrote:
> I don't mind helping to maintain it under any of those teams. Thank you Andreas for taking care about this new dependency. I will look into updating pandas package
That's very welcome and help is actually needed. I have pushed my
preliminary attempt to Debian Science Git[1]. Since the test suite was
featuring four errors I simply forced the result of dh_auto_test to true
to get some package for a first test. This needs to be investigated
before uploading. Unfortunately the install process also throws errors
when compyling to byte code. Here are the issues I'm facing and I'm
struck with:
1) test suite
I: pybuild base:184: cd /build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest tests
============================= test session starts ==============================
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /build/python-aws-xray-sdk-0.95, inifile:
collected 57 items / 4 errors
==================================== ERRORS ====================================
ERROR collecting .pybuild/pythonX.Y_2.7/build/tests/test_async_local_storage.py.
/usr/lib/python2.7/dist-packages/_pytest/python.py:395: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python2.7/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/test_async_local_storage.py", line 10
E async def _test():
E ^
E SyntaxError: invalid syntax
__ ERROR collecting .pybuild/pythonX.Y_2.7/build/tests/test_async_recorder.py __
/usr/lib/python2.7/dist-packages/_pytest/python.py:395: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python2.7/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/test_async_recorder.py", line 9
E async def async_method2():
E ^
E SyntaxError: invalid syntax
ERROR collecting .pybuild/pythonX.Y_2.7/build/tests/ext/aiobotocore/test_aiobotocore.py.
/usr/lib/python2.7/dist-packages/_pytest/python.py:395: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python2.7/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/ext/aiobotocore/test_aiobotocore.py", line 24
E async def test_describe_table(loop, recorder):
E ^
E SyntaxError: invalid syntax
ERROR collecting .pybuild/pythonX.Y_2.7/build/tests/ext/aiohttp/test_aiohttp.py.
/usr/lib/python2.7/dist-packages/_pytest/python.py:395: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python2.7/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/ext/aiohttp/test_aiohttp.py", line 46
E async def handle_ok(self, request: web.Request) -> web.Response:
E ^
E SyntaxError: invalid syntax
!!!!!!!!!!!!!!!!!!! Interrupted: 4 errors during collection !!!!!!!!!!!!!!!!!!!!
=========================== 4 error in 0.69 seconds ============================
2) installation of the resulting package:
E:Sub-process /usr/bin/dpkg returned an error code (1)
Traceback (most recent call last):
File "/usr/share/wajig/debfile-deps.py", line 56, in <module>
main(sys.argv[1])
File "/usr/share/wajig/debfile-deps.py", line 48, in main
cache.commit(apt.progress.text.AcquireProgress())
File "/usr/lib/python3/dist-packages/apt/cache.py", line 529, in commit
raise SystemError("installArchives() failed")
SystemError: installArchives() failed
python-aws-xray-sdk (0.95-1) wird eingerichtet ...
File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/core/async_context.py", line 14
def __init__(self, *args, loop=None, use_task_factory=True, **kwargs):
^
SyntaxError: invalid syntax
File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/core/async_recorder.py", line 20
async def wrapper(wrapped, instance, args, kwargs):
^
SyntaxError: invalid syntax
File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/ext/aiobotocore/patch.py", line 30
async def _xray_traced_aiobotocore(wrapped, instance, args, kwargs):
^
SyntaxError: invalid syntax
File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/ext/aiohttp/middleware.py", line 11
async def middleware(app, handler):
^
SyntaxError: invalid syntax
Any help would be really appreciated.
Kind regards
Andreas.
[1] https://salsa.debian.org/science-team/python-aws-xray-sdk.git
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Simon McVittie <smcv@debian.org> |
|---|---|
| Date | 2018-01-15 13:30 +0100 |
| Subject | Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8c3L-1tj-5@gated-at.bofh.it> |
| In reply to | #10053 |
On Mon, 15 Jan 2018 at 12:59:29 +0100, Andreas Tille wrote:
> E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/test_async_local_storage.py", line 10
> E async def _test():
> E ^
> E SyntaxError: invalid syntax
Looks like it needs python3 >= 3.5. https://www.google.com/search?q=async%20def
> python-aws-xray-sdk (0.95-1) wird eingerichtet ...
> File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/core/async_context.py", line 14
> def __init__(self, *args, loop=None, use_task_factory=True, **kwargs):
> ^
> SyntaxError: invalid syntax
That's Python 3 syntax too. https://www.python.org/dev/peps/pep-3102/
smcv
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-15 13:50 +0100 |
| Subject | Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8cn8-1C4-11@gated-at.bofh.it> |
| In reply to | #10054 |
Hi Simon & Tristan (racing condition with same answer),
On Mon, Jan 15, 2018 at 12:21:02PM +0000, Simon McVittie wrote:
> On Mon, 15 Jan 2018 at 12:59:29 +0100, Andreas Tille wrote:
> > E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/test_async_local_storage.py", line 10
> > E async def _test():
> > E ^
> > E SyntaxError: invalid syntax
>
> Looks like it needs python3 >= 3.5. https://www.google.com/search?q=async%20def
>
> > python-aws-xray-sdk (0.95-1) wird eingerichtet ...
> > File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/core/async_context.py", line 14
> > def __init__(self, *args, loop=None, use_task_factory=True, **kwargs):
> > ^
> > SyntaxError: invalid syntax
>
> That's Python 3 syntax too. https://www.python.org/dev/peps/pep-3102/
Setup.py of the package says:
...
'Programming Language :: Python',
'Programming Language :: Python :: 2',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5',
'Programming Language :: Python :: 3.6',
...
In the end we actually need this also for Python 2.7 since python-pandas
is also 2.7 and Python 3 (and several reverse depends of python-pandas
need 2.7 as well). Seems I need to open an issue on Github.
Further question: It seems my packaging is broken since the test is only
run on Python 2.7 (and is breaking there as you know). What am I missing
to run the Python 3 tests?
Kind regards
Andreas.
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Tristan Seligmann <mithrandi@mithrandi.net> |
|---|---|
| Date | 2018-01-15 13:30 +0100 |
| Subject | Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8bU5-1pj-3@gated-at.bofh.it> |
| In reply to | #10053 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, 15 Jan 2018 at 13:59 Andreas Tille <andreas@an3as.eu> wrote: > SyntaxError: invalid syntax > !!!!!!!!!!!!!!!!!!! Interrupted: 4 errors during collection > !!!!!!!!!!!!!!!!!!!! > All of these syntax errors relate to syntax that only exist on Python 3, thus I would conclude that this package does not support Python 2.
[toc] | [prev] | [next] | [standalone]
| From | Piotr Ożarowski <piotr@debian.org> |
|---|---|
| Date | 2018-01-15 14:00 +0100 |
| Subject | Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8cwN-1G5-5@gated-at.bofh.it> |
| In reply to | #10053 |
[Andreas Tille, 2018-01-15]
> 1) test suite
>
> I: pybuild base:184: cd /build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest tests
> ============================= test session starts ==============================
> platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
> rootdir: /build/python-aws-xray-sdk-0.95, inifile:
> collected 57 items / 4 errors
>
> ==================================== ERRORS ====================================
> ERROR collecting .pybuild/pythonX.Y_2.7/build/tests/test_async_local_storage.py.
> /usr/lib/python2.7/dist-packages/_pytest/python.py:395: in _importtestmodule
> mod = self.fspath.pyimport(ensuresyspath=importmode)
> /usr/lib/python2.7/dist-packages/py/_path/local.py:662: in pyimport
> __import__(modname)
> E File "/build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build/tests/test_async_local_storage.py", line 10
> E async def _test():
> E ^
> E SyntaxError: invalid syntax
async (and all aio* libs in other tests) is not available in Python 2.7
so simply disable them. You can do this in debian/rules:
export PYBUILD_TEST_ARGS_python2=--ignore tests/test_async_local_storage.py --ignore tests/test_async_recorder.py --ignore tests/ext/aiobotocore/ --ignore tests/ext/aiohttp/
> 2) installation of the resulting package:
>
> E:Sub-process /usr/bin/dpkg returned an error code (1)
> Traceback (most recent call last):
> File "/usr/share/wajig/debfile-deps.py", line 56, in <module>
> main(sys.argv[1])
> File "/usr/share/wajig/debfile-deps.py", line 48, in main
> cache.commit(apt.progress.text.AcquireProgress())
> File "/usr/lib/python3/dist-packages/apt/cache.py", line 529, in commit
> raise SystemError("installArchives() failed")
> SystemError: installArchives() failed
> python-aws-xray-sdk (0.95-1) wird eingerichtet ...
> File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/core/async_context.py", line 14
> def __init__(self, *args, loop=None, use_task_factory=True, **kwargs):
> ^
> SyntaxError: invalid syntax
>
> File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/core/async_recorder.py", line 20
> async def wrapper(wrapped, instance, args, kwargs):
> ^
> SyntaxError: invalid syntax
>
> File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/ext/aiobotocore/patch.py", line 30
> async def _xray_traced_aiobotocore(wrapped, instance, args, kwargs):
> ^
> SyntaxError: invalid syntax
>
> File "/usr/lib/python2.7/dist-packages/aws_xray_sdk/ext/aiohttp/middleware.py", line 11
> async def middleware(app, handler):
> ^
> SyntaxError: invalid syntax
similar issue here, async stuff will not work in 2.7, you can tell
dh_python2 to remove these files by adding
debian/python-aws-xray-sdk.pyremove file containing:
aws_xray_sdk/core/async_*
aws_xray_sdk/ext/aiobotocore/
aws_xray_sdk/ext/aiohttp/
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-15 16:10 +0100 |
| Subject | Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8eyC-3gz-17@gated-at.bofh.it> |
| In reply to | #10057 |
Hi Piotr,
On Mon, Jan 15, 2018 at 01:52:27PM +0100, Piotr Ożarowski wrote:
> async (and all aio* libs in other tests) is not available in Python 2.7
> so simply disable them. You can do this in debian/rules:
>
> export PYBUILD_TEST_ARGS_python2=--ignore tests/test_async_local_storage.py --ignore tests/test_async_recorder.py --ignore tests/ext/aiobotocore/ --ignore tests/ext/aiohttp/
Ahh, very helpful hint!
Now I need to exclude those tests that try to access remote network
locations but I failed with the same method as you proposed above.
Any clue how I can do that properly (please Git pull to see my failed
attempts).
Kind regards
Andreas.
[1] https://salsa.debian.org/science-team/python-aws-xray-sdk.git
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Piotr Ożarowski <piotr@debian.org> |
|---|---|
| Date | 2018-01-15 16:20 +0100 |
| Subject | Re: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team) |
| Message-ID | <v8eIh-3kb-25@gated-at.bofh.it> |
| In reply to | #10058 |
[Andreas Tille, 2018-01-15] > Now I need to exclude those tests that try to access remote network > locations but I failed with the same method as you proposed above. > > Any clue how I can do that properly (please Git pull to see my failed > attempts). if you want to disable specific test (not the whole file) in pytest, use "-k-somename" (note the "-" after "-k") -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-16 21:50 +0100 |
| Subject | Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random' |
| Message-ID | <v8Glb-5um-1@gated-at.bofh.it> |
| In reply to | #10059 |
Hi,
when continuing to check preconditions for python-moto my next target
is python-jsondiff[1]. When trying to build I get:
...
I: pybuild base:184: cd /build/python-jsondiff-1.1.1/.pybuild/pythonX.Y_3.6/build; python3.6 -m unittest discover -v
tests (unittest.loader._FailedTest) ... ERROR
======================================================================
ERROR: tests (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: tests
Traceback (most recent call last):
File "/usr/lib/python3.6/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.6/unittest/loader.py", line 369, in _get_module_from_name
__import__(name)
File "/build/python-jsondiff-1.1.1/.pybuild/pythonX.Y_3.6/build/tests/__init__.py", line 7, in <module>
from nose_random import randomize
ModuleNotFoundError: No module named 'nose_random'
----------------------------------------------------------------------
Ran 1 test in 0.000s
...
My web search for a module named 'nose_random' remained empty.
Any idea what might be wrong here?
Kind regards
Andreas.
[1] https://salsa.debian.org/science-team/python-jsondiff.git
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Tristan Seligmann <mithrandi@mithrandi.net> |
|---|---|
| Date | 2018-01-17 08:20 +0100 |
| Subject | Re: Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random' |
| Message-ID | <v8Q1b-3Ja-1@gated-at.bofh.it> |
| In reply to | #10063 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, 16 Jan 2018 at 22:45 Andreas Tille <andreas@an3as.eu> wrote: > My web search for a module named 'nose_random' remained empty. > I found this package, which seems to match, from the same organization: https://github.com/ZoomerAnalytics/nose-random Unfortunately it seems to be unreleased, so I think you would need to package a GitHub snapshot or something (or alternatively disable the tests).
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-17 11:20 +0100 |
| Subject | Re: Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random' |
| Message-ID | <v8SZ3-5Pk-1@gated-at.bofh.it> |
| In reply to | #10064 |
Hi Tristan,
On Wed, Jan 17, 2018 at 06:56:00AM +0000, Tristan Seligmann wrote:
> I found this package, which seems to match, from the same organization:
> https://github.com/ZoomerAnalytics/nose-random
>
> Unfortunately it seems to be unreleased, so I think you would need to
> package a GitHub snapshot or something (or alternatively disable the tests).
Thanks for the hint. I think for the moment I'll skip the test but I
have opened an issue asking for release tags[1].
Kind regards
Andreas.
[1] https://github.com/ZoomerAnalytics/nose-random/issues/1
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@fam-tille.de> |
|---|---|
| Date | 2018-02-02 09:30 +0100 |
| Subject | Bug#777089: Preconditions for python-moto finished - help needed to build package itself |
| Message-ID | <veETn-2xd-3@gated-at.bofh.it> |
| In reply to | #10065 |
Hi,
as you might have noticed I finalised the preconditions to build
python-moto which is in salsa.d.o[1]. When trying to build I get:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py test
running test
running egg_info
writing requirements to moto.egg-info/requires.txt
writing moto.egg-info/PKG-INFO
writing top-level names to moto.egg-info/top_level.txt
writing dependency_links to moto.egg-info/dependency_links.txt
writing entry points to moto.egg-info/entry_points.txt
reading manifest file 'moto.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'moto.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
File "setup.py", line 68, in <module>
"Topic :: Software Development :: Testing",
File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 129, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 226, in run
self.run_tests()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 248, in run_tests
exit=False,
File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
self.createTests()
File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
self.module)
File "/usr/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python2.7/unittest/loader.py", line 103, in loadTestsFromName
return self.loadTestsFromModule(obj)
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 52, in loadTestsFromModule
tests.append(self.loadTestsFromName(submodule))
File "/usr/lib/python2.7/unittest/loader.py", line 100, in loadTestsFromName
parent, obj = obj, getattr(obj, part)
AttributeError: 'module' object has no attribute 'backport_assert_raises'
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I was seeking for some missing backport module but I have no real clue
what might be missing. Any help would be welcome.
Kind regards
Andreas.
[1]
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Olivier Sallou <olivier.sallou@irisa.fr> |
|---|---|
| Date | 2018-02-02 10:20 +0100 |
| Subject | Bug#777089: Preconditions for python-moto finished - help needed to build package itself |
| Message-ID | <veFFL-32O-1@gated-at.bofh.it> |
| In reply to | #10098 |
----- Mail original -----
> De: "Andreas Tille" <andreas@fam-tille.de>
> À: 777089@bugs.debian.org
> Cc: debian-python@lists.debian.org, "Debian Science List" <debian-science@lists.debian.org>
> Envoyé: Vendredi 2 Février 2018 09:16:55
> Objet: Preconditions for python-moto finished - help needed to build package itself
>
> Hi,
>
> as you might have noticed I finalised the preconditions to build
> python-moto which is in salsa.d.o[1]. When trying to build I get:
>
>
>
> dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test
> running test
> running egg_info
> writing requirements to moto.egg-info/requires.txt
> writing moto.egg-info/PKG-INFO
> writing top-level names to moto.egg-info/top_level.txt
> writing dependency_links to moto.egg-info/dependency_links.txt
> writing entry points to moto.egg-info/entry_points.txt
> reading manifest file 'moto.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'moto.egg-info/SOURCES.txt'
> running build_ext
> Traceback (most recent call last):
> File "setup.py", line 68, in <module>
> "Topic :: Software Development :: Testing",
> File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 129,
> in setup
> return distutils.core.setup(**attrs)
> File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
> dist.run_commands()
> File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
> File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line
> 226, in run
> self.run_tests()
> File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line
> 248, in run_tests
> exit=False,
> File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
> self.parseArgs(argv)
> File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
> self.createTests()
> File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
> self.module)
> File "/usr/lib/python2.7/unittest/loader.py", line 130, in
> loadTestsFromNames
> suites = [self.loadTestsFromName(name, module) for name in names]
> File "/usr/lib/python2.7/unittest/loader.py", line 103, in
> loadTestsFromName
> return self.loadTestsFromModule(obj)
> File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line
> 52, in loadTestsFromModule
> tests.append(self.loadTestsFromName(submodule))
> File "/usr/lib/python2.7/unittest/loader.py", line 100, in
> loadTestsFromName
> parent, obj = obj, getattr(obj, part)
> AttributeError: 'module' object has no attribute 'backport_assert_raises'
backport_assert_raises is a python file in tests directory of moto, maybe it is missing in your install?
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1:
> python2.7 setup.py test
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:6: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
>
>
> I was seeking for some missing backport module but I have no real clue
> what might be missing. Any help would be welcome.
>
> Kind regards
>
> Andreas.
>
>
>
> [1]
>
> --
> http://fam-tille.de
>
>
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2018-01-22 15:10 +0100 |
| Subject | Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref |
| Message-ID | <vaKXn-5QB-1@gated-at.bofh.it> |
| In reply to | #10063 |
Hi,
I kept on working packaging python-moto predependencies. I'm now
stumbling upon python-backports.tempfile[1] and
python-backports.weakref[2]. My naive packaging attempt puts
the modules into
/usr/lib/python*/dist-packages/backports
leaving the same package
/usr/lib/python3/dist-packages/backports/__init__.py
for both packages and thus the packages are conflicting. I have no idea
why pybuild simply uses the dir backports instead of the full module
name nor do I have any idea how to fix this. I tried to hack around in
the backports.weakref package using
override_dh_auto_install:
for dir in `find .pybuild -type d -name backports | sort | uniq` ; do \
mv $${dir} $${dir}.weakref ; \
done
dh_auto_install
but this rather has led to an empty package.
Any help is welcome
Andreas.
[1] https://salsa.debian.org/science-team/python-backports.tempfile.git
[2] https://salsa.debian.org/science-team/python-backports.weakref.git
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Piotr Ożarowski <piotr@debian.org> |
|---|---|
| Date | 2018-01-22 15:30 +0100 |
| Subject | Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref |
| Message-ID | <vaLgK-5Z2-7@gated-at.bofh.it> |
| In reply to | #10079 |
[Andreas Tille, 2018-01-22] > Hi, > > I kept on working packaging python-moto predependencies. I'm now > stumbling upon python-backports.tempfile[1] and > python-backports.weakref[2]. My naive packaging attempt puts > the modules into > > /usr/lib/python*/dist-packages/backports > > leaving the same package > > /usr/lib/python3/dist-packages/backports/__init__.py if it's an empty file (or can be removed, as most probably in this case) you can tell dh_python2 to handle the namespace for you with: override_dh_python2: dh_python2 --namespace backports For Python 3, __init__.py is not needed anymore, so you can simply remove it in both packages by creating debian/python3-foo.pyremove file with "backports/__init__.py" > for both packages and thus the packages are conflicting. I have no idea > why pybuild simply uses the dir backports instead of the full module that's how Python works, nothing to do with pybuild -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[toc] | [prev] | [next] | [standalone]
| From | Olivier Sallou <olivier.sallou@irisa.fr> |
|---|---|
| Date | 2018-01-23 17:20 +0100 |
| Subject | Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref |
| Message-ID | <vb9sJ-4vm-1@gated-at.bofh.it> |
| In reply to | #10079 |
----- Mail original -----
> De: "Andreas Tille" <andreas@an3as.eu>
> À: debian-python@lists.debian.org, "Debian Science List" <debian-science@lists.debian.org>, 777089@bugs.debian.org
> Envoyé: Lundi 22 Janvier 2018 15:04:10
> Objet: Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting
> python-backports.weakref
>
> Hi,
>
> I kept on working packaging python-moto predependencies. I'm now
> stumbling upon python-backports.tempfile[1] and
> python-backports.weakref[2]. My naive packaging attempt puts
> the modules into
well, package name should not really use dots in name, I suppose that's what leads to error. But don't know how to fix that with python helper... :-(
both modules use the same "base module", ie *backports* so final dest is correct. From a pure python point of view, you can "merge" multiple sub modules in the same mail module, python will manage the duplication of __init__.py
However, in Debian case, I do not know how this can be handled as 2 packages cannot hold the same file (even if __init__ is only an empty file), and at least one must be present (if you install only one).
Olivier
>
> /usr/lib/python*/dist-packages/backports
>
> leaving the same package
>
> /usr/lib/python3/dist-packages/backports/__init__.py
>
> for both packages and thus the packages are conflicting. I have no idea
> why pybuild simply uses the dir backports instead of the full module
> name nor do I have any idea how to fix this. I tried to hack around in
> the backports.weakref package using
>
>
> override_dh_auto_install:
> for dir in `find .pybuild -type d -name backports | sort | uniq` ; do
> \
> mv $${dir} $${dir}.weakref ; \
> done
> dh_auto_install
>
> but this rather has led to an empty package.
>
> Any help is welcome
>
> Andreas.
>
>
> [1] https://salsa.debian.org/science-team/python-backports.tempfile.git
> [2] https://salsa.debian.org/science-team/python-backports.weakref.git
>
> --
> http://fam-tille.de
>
>
[toc] | [prev] | [next] | [standalone]
| From | Olivier Sallou <olivier.sallou@irisa.fr> |
|---|---|
| Date | 2018-01-26 16:20 +0100 |
| Subject | Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref |
| Message-ID | <vcdXk-4Xj-11@gated-at.bofh.it> |
| In reply to | #10083 |
----- Mail original -----
> De: "Olivier Sallou" <olivier.sallou@irisa.fr>
> À: "Andreas Tille" <andreas@an3as.eu>
> Cc: debian-python@lists.debian.org, "Debian Science List" <debian-science@lists.debian.org>, 777089@bugs.debian.org
> Envoyé: Mardi 23 Janvier 2018 17:11:05
> Objet: Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting
> python-backports.weakref
>
>
>
> ----- Mail original -----
> > De: "Andreas Tille" <andreas@an3as.eu>
> > À: debian-python@lists.debian.org, "Debian Science List"
> > <debian-science@lists.debian.org>, 777089@bugs.debian.org
> > Envoyé: Lundi 22 Janvier 2018 15:04:10
> > Objet: Re: Next python-mote pre-condition - issue with pybuild:
> > python-backports.tempfile conflicting
> > python-backports.weakref
> >
> > Hi,
> >
> > I kept on working packaging python-moto predependencies. I'm now
> > stumbling upon python-backports.tempfile[1] and
> > python-backports.weakref[2]. My naive packaging attempt puts
> > the modules into
>
> well, package name should not really use dots in name, I suppose that's what
> leads to error. But don't know how to fix that with python helper... :-(
>
> both modules use the same "base module", ie *backports* so final dest is
> correct. From a pure python point of view, you can "merge" multiple sub
> modules in the same mail module, python will manage the duplication of
> __init__.py
>
> However, in Debian case, I do not know how this can be handled as 2 packages
> cannot hold the same file (even if __init__ is only an empty file), and at
> least one must be present (if you install only one).
>
> Olivier
>
> >
> > /usr/lib/python*/dist-packages/backports
> >
> > leaving the same package
> >
> > /usr/lib/python3/dist-packages/backports/__init__.py
after thinking about this, I think the "easy" solution would be to:
* create a *backports* package, that simply embeds a backports/__init__.py
* depends on this backports package itself and simply remove backports/__init__.py from backports.XXX packages.
If they depend on backports, this file will will always be present, and will be of for backports.xx modules.
You would only need to remove the file from installed files in packages.
I see though that you have already uploaded package, how did you handle the issue?
Olivier
> >
> > for both packages and thus the packages are conflicting. I have no idea
> > why pybuild simply uses the dir backports instead of the full module
> > name nor do I have any idea how to fix this. I tried to hack around in
> > the backports.weakref package using
> >
> >
> > override_dh_auto_install:
> > for dir in `find .pybuild -type d -name backports | sort | uniq` ;
> > do
> > \
> > mv $${dir} $${dir}.weakref ; \
> > done
> > dh_auto_install
> >
> > but this rather has led to an empty package.
> >
> > Any help is welcome
> >
> > Andreas.
> >
> >
> > [1] https://salsa.debian.org/science-team/python-backports.tempfile.git
> > [2] https://salsa.debian.org/science-team/python-backports.weakref.git
> >
> > --
> > http://fam-tille.de
> >
> >
>
>
[toc] | [prev] | [next] | [standalone]
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Date | 2018-01-26 17:10 +0100 |
| Subject | Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref |
| Message-ID | <vceJH-5vz-11@gated-at.bofh.it> |
| In reply to | #10089 |
> after thinking about this, I think the "easy" solution would be to: > > * create a *backports* package, that simply embeds a backports/__init__.py > > * depends on this backports package itself and simply remove backports/__init__.py from backports.XXX packages. > > If they depend on backports, this file will will always be present, and will be of for backports.xx modules. that requires a lot of coordination with all the other backports packages. currently (well, before tempfile) there was no package installing backports/__init__.py and every package was (correctly) using dh_python2 --namespace > You would only need to remove the file from installed files in packages. > > I see though that you have already uploaded package, how did you handle the issue? simple, he didnt :/ Andreas, please re-upload backports.tempfile using dh_python2 --namespace so taht this package will nicely fit with the existing backports packages. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web