Re: Bug#937177: obitools: Python2 removal in sid/bullseye

2020-03-05 Thread Sandro Tosi
> > This
> > package is blocking several others.  Would it be best to remove it?  It can
> > always be re-introduced if a python3 port appears.
>
> Since some time I've pushed a 2to3 based port to Git.  I've now fixed
> some issues of this and I wonder whether we might give it a try to do
> the port inside Debian.

It looks like Olivier committed a py3k port on debmed almost a month
ago: Olivier, do you have any plan to complete (if necessary) and
upload this package soon? it would help with the py2removal effort.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Help for issues with lazyarray needed

2020-03-05 Thread Andreas Tille
On Thu, Mar 05, 2020 at 02:27:13PM +0530, Nilesh Patra wrote:
> 
> I had tried this,
> I think Passing [:-1] in the mask2 initialisation would fix this. We also
> need to cast this into a numpy array.
> ...
> 
> I'll try this by midnight today. If I can, I'll try a fix for this, and
> make a MR, or a patch.
> Would that work?

No need to work on this any more.  Upstream pointed me to Gitlab where
development is continued.  Status in Git is fine now.  Thanks a lot for
your attempt to help

 Andreas.

-- 
http://fam-tille.de



Re: Help for issues with lazyarray needed

2020-03-05 Thread Nilesh Patra
On Thu, 5 Mar 2020, 14:16 Andreas Tille,  wrote:

> Control: tags -1 pending
>
> Hi,
>
> I have updated lazyarray in Git[1] (by moving it to Debian Science
> team).  The old package was lagging way behind upstream and a Python3
> port is available by upstream so I just create the python3-lazyarray
> package fixing the open bugs.
>
> Unfortunately there is an open issue[2].  Since the latest upstream
> commit has only one failure (in contrast to the latest tagges upstream
> version which is according to commit logs not really the latest) I
> based the source tarball on the latest commit.  Unfortunately there
> is one remaining issue for Python3.7 and two for Python3.8
>
>
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd
> /build/lazyarray-2.10.0+hg20170630.23ccca1/.pybuild/cpython3_3.7_lazyarray/build;
> python3.7 -m nose -v test
> test.test_lazyarray.test_create_with_int ... ok
> ...
> ==
> FAIL: test.test_lazyarray.test__issue4
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File
> "/build/lazyarray-2.10.0+hg20170630.23ccca1/.pybuild/cpython3_3.7_lazyarray/build/test/test_lazyarray.py",
> line 701, in test__issue4
> assert_equal(b[mask1].shape, partial_shape(mask1, b.shape),
> a[mask1].shape)
> AssertionError: Tuples differ: (4, 1, 3) != (4,)
>




> First tuple contains 2 additional elements.
> First extra element 1:
> 1
>
> - (4, 1, 3)
> + (4,) : (4, 1, 3)
>
> --
> Ran 87 tests in 0.027s
>
> FAILED (failures=1)
>

I had tried this,
I think Passing [:-1] in the mask2 initialisation would fix this. We also
need to cast this into a numpy array.


>
>
> I continued manually in the pbuilder chroot to get Python3.8 issues:
>
> pbuilder-chroot# cd
> /build/lazyarray-2.10.0+hg20170630.23ccca1/.pybuild/cpython3_3.8_lazyarray/build;
> python3.8 -m nose -v test
> ...
> ==
> ERROR: test.support.testresult.get_test_runner_class
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
> TypeError: get_test_runner_class() missing 1 required positional argument:
> 'verbosity'
>
> ==
> ERROR: test.support.testresult.get_test_runner
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
> TypeError: get_test_runner() missing 2 required positional arguments:
> 'stream' and 'verbosity'
>
> --
> Ran 45 tests in 7.327s
>
> FAILED (SKIP=1, errors=2)
>

I'll try this by midnight today. If I can, I'll try a fix for this, and
make a MR, or a patch.
Would that work?


> I somehow suspect that the latter issue is not really hard and I wonder
> whether I can get some help from DPMT?
>
> My current plan is to ignore the test suite errors for the moment,
> upload a Python3 enabled package to new queue.  Once it has passed new I
> will see whether we found some solution for the said issues.  If not
> I'll file a new RC bug to prevent testing migration.  I'd like to do
> that means to get the latest version of pynn built to keep on with the
> Python3 migration for this package.
>
> Any help for the remaining issues is welcome.
>
> Kind regards
>
>   Andreas.
>
> [1] https://salsa.debian.org/science-team/lazyarray
> [2] https://bitbucket.org/apdavison/lazyarray/issues/6/test-failure
>
> --
> http://fam-tille.de
>
>


Help for issues with lazyarray needed

2020-03-05 Thread Andreas Tille
Control: tags -1 pending

Hi,

I have updated lazyarray in Git[1] (by moving it to Debian Science
team).  The old package was lagging way behind upstream and a Python3
port is available by upstream so I just create the python3-lazyarray
package fixing the open bugs.

Unfortunately there is an open issue[2].  Since the latest upstream
commit has only one failure (in contrast to the latest tagges upstream
version which is according to commit logs not really the latest) I
based the source tarball on the latest commit.  Unfortunately there
is one remaining issue for Python3.7 and two for Python3.8


   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd 
/build/lazyarray-2.10.0+hg20170630.23ccca1/.pybuild/cpython3_3.7_lazyarray/build;
 python3.7 -m nose -v test
test.test_lazyarray.test_create_with_int ... ok
...
==
FAIL: test.test_lazyarray.test__issue4
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/lazyarray-2.10.0+hg20170630.23ccca1/.pybuild/cpython3_3.7_lazyarray/build/test/test_lazyarray.py",
 line 701, in test__issue4
assert_equal(b[mask1].shape, partial_shape(mask1, b.shape), a[mask1].shape)
AssertionError: Tuples differ: (4, 1, 3) != (4,)

First tuple contains 2 additional elements.
First extra element 1:
1

- (4, 1, 3)
+ (4,) : (4, 1, 3)

--
Ran 87 tests in 0.027s

FAILED (failures=1)



I continued manually in the pbuilder chroot to get Python3.8 issues:

pbuilder-chroot# cd 
/build/lazyarray-2.10.0+hg20170630.23ccca1/.pybuild/cpython3_3.8_lazyarray/build;
 python3.8 -m nose -v test
...
==
ERROR: test.support.testresult.get_test_runner_class
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
TypeError: get_test_runner_class() missing 1 required positional argument: 
'verbosity'

==
ERROR: test.support.testresult.get_test_runner
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
TypeError: get_test_runner() missing 2 required positional arguments: 'stream' 
and 'verbosity'

--
Ran 45 tests in 7.327s

FAILED (SKIP=1, errors=2)


I somehow suspect that the latter issue is not really hard and I wonder
whether I can get some help from DPMT?

My current plan is to ignore the test suite errors for the moment,
upload a Python3 enabled package to new queue.  Once it has passed new I
will see whether we found some solution for the said issues.  If not
I'll file a new RC bug to prevent testing migration.  I'd like to do
that means to get the latest version of pynn built to keep on with the
Python3 migration for this package.

Any help for the remaining issues is welcome.

Kind regards

  Andreas.

[1] https://salsa.debian.org/science-team/lazyarray
[2] https://bitbucket.org/apdavison/lazyarray/issues/6/test-failure

-- 
http://fam-tille.de