[Debian-med-packaging] Bug#802354: Help needed: Bug#802354: python-matplotlib-venn: FTBFS: AttributeError: can't set attribute

[Andreas Tille]

Hi Konstantin,

the full story of the problem with tests can be read here:

   https://bugs.debian.org/802354

I'll keep you updated if we find a solution but may be you might have
one yourself and can help solving the issue.

On Tue, Oct 20, 2015 at 07:37:57AM +0200, Olivier Sallou wrote:
> > The package fails to build:
> >
> > ========================== 49 passed in 1.17 seconds ===========================
> > 	pybuild --test --test-pytest -i python{version} -p 3.4 --test --system=custom "--test-args=cp -a README.rst {home_dir}/build && cd {home_dir}/build && {interpreter} /python-matplotlib-venn-0.11/setup.py test && rm README.rst" --dir .
> > I: pybuild base:170: cp -a README.rst /python-matplotlib-venn-0.11/.pybuild/pythonX.Y_3.4/build && cd /python-matplotlib-venn-0.11/.pybuild/pythonX.Y_3.4/build && python3.4 /python-matplotlib-venn-0.11/setup.py test && rm README.rst
> > running test
> > Traceback (most recent call last):
> >   File "/python-matplotlib-venn-0.11/setup.py", line 56, in <module>
> >     entry_points=''
> I am not an expert, but it seems that entry_points is expected to be a
> dict ( = {} ) . As it is empty, I think it could just be removed.

The problematic chunk is probably not entry_points but rather

   self.test_args = []
 
> Olivier
> >   File "/usr/lib/python3.4/distutils/core.py", line 148, in setup
> >     dist.run_commands()
> >   File "/usr/lib/python3.4/distutils/dist.py", line 955, in run_commands
> >     self.run_command(cmd)
> >   File "/usr/lib/python3.4/distutils/dist.py", line 973, in run_command
> >     cmd_obj.ensure_finalized()
> >   File "/usr/lib/python3.4/distutils/cmd.py", line 107, in ensure_finalized
> >     self.finalize_options()
> >   File "/python-matplotlib-venn-0.11/setup.py", line 21, in finalize_options
> >     self.test_args = []
> > AttributeError: can't set attribute

I tried a web search for this kind of error and found

   https://github.com/marshmallow-code/marshmallow/issues/300

which was solved in this patch

   https://github.com/marshmallow-code/marshmallow/commit/1dbcae9c439d1a268717feb089351fc3c5180ac3#diff-2eeaed663bd0d25b7e608891384b7298

I tried to implement this idea in python-matplotlib-venn but the change
relies on the existence of a dir tests/ which is not part of the download
tarball (but of the upstream Git repository[1]).

If I apply the attached patch *and* copy the tests/ dir from upstream
Git repository I get


$ python3.4 setup.py test
running test
Searching for pytest
Best match: pytest 2.8.2
Processing pytest-2.8.2-py3.4.egg

Using /home/andreas/debian-maintain/repack/python-matplotlib-venn/python-matplotlib-venn-0.11/.eggs/pytest-2.8.2-py3.4.egg
Searching for py>=1.4.29
Best match: py 1.4.30
Processing py-1.4.30-py3.4.egg

Using /home/andreas/debian-maintain/repack/python-matplotlib-venn/python-matplotlib-venn-0.11/.eggs/py-1.4.30-py3.4.egg
running egg_info
writing dependency_links to matplotlib_venn.egg-info/dependency_links.txt
writing top-level names to matplotlib_venn.egg-info/top_level.txt
writing requirements to matplotlib_venn.egg-info/requires.txt
writing matplotlib_venn.egg-info/PKG-INFO
reading manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK


Hmmm, doing all the things without any test run does not seem sensible.

I'm out of ideas now and any help would be welcome.

Kind regards

       Andreas.

[1] https://github.com/konstantint/matplotlib-venn

-- 
http://fam-tille.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: marshmallow.patch
Type: text/x-diff
Size: 2978 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20151020/1ce716a8/attachment.patch>