Bug 735478

I'm just curious, what fails in numpy-1.5.1 so I'm building it on f15 to see the failure :)

%check is missing for python3 (currently untested):
%if 0%{?with_python3}
pushd %{py3dir}
mkdir test
cd test
PYTHONPATH=$RPM_BUILD_ROOT%{python3_sitearch} python3 -c "import scipy; scip    y.test('full')"
popd
%endif # with_python3

Stuff like this:

atlas_blas_threads_info:
Setting PTATLAS=ATLAS
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib64/atlas
  libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib64
  libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib64/atlas
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib64/sse2
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib64
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib/sse2
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib
  NOT AVAILABLE

The errors occur even though the libraries exist.  I found that I could produce the errors more directly by running the following after unpacking:

ATLAS=/usr/lib64/atlas BLAS=/usr/lib64 python3 setup.py config_fc --fcompiler=gnu95 --noarch build

I looked through the file /usr/lib64/python3.2/site-packages/numpy/distutils/system_info.py but I'm unfamiliar enough with this code that it would take a while to track down. Once I figured out that it's working in numpy 1.6, I figured it wasn't worth taking the time to track down a bug that's already been tracked down. :)

By the way, if to build on Fedora 15, you'll have to change the 15 to something else in the top line of the spec file, i.e.:

%if (0%{?fedora} > 14 || 0%{?rhel} > 5)

(In reply to comment #2)
> /usr/lib64/python3.2/site-packages/numpy/distutils/system_info.py but I'm
> unfamiliar enough with this code that it would take a while to track down. Once
> I figured out that it's working in numpy 1.6, I figured it wasn't worth taking
> the time to track down a bug that's already been tracked down. :)

Yes, +1^^

Comments about your patch:
* python is called everywhere, so it would be better to just call python3 too.
* I added the test section for python3
* There was a problem with "summary" in the top line.

SPEC: http://tomspur.fedorapeople.org/scipy.spec
DIFF: http://tomspur.fedorapeople.org/scipy-diff2master

scratch build for f17:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3321943

When the tests pass, I think it's ok to build it in rawhide and f16.
Andrew, thanks for testing on f16 :)

Other comments?

(In reply to comment #4)
> * python is called everywhere, so it would be better to just call python3 too.

As far as I can tell from the Python packaging guidelines, the %{__python3} macro is the preferred approach.  I think it might be better to switch the "python" calls to %{__python} than to get rid of the %{__python3} macros.

> * I added the test section for python3

Yes, I noticed this was missing after I posted the patch.  Your test section looks right to me.

> * There was a problem with "summary" in the top line.

I'm afraid I can't find the problem you're referring to.


> When the tests pass, I think it's ok to build it in rawhide and f16.
> Andrew, thanks for testing on f16 :)

Glad I can help.


> Other comments?

I can't think of anything else. Thanks for looking at this so quickly.

(In reply to comment #5)
> (In reply to comment #4)
> > * python is called everywhere, so it would be better to just call python3 too.
> 
> As far as I can tell from the Python packaging guidelines, the %{__python3}
> macro is the preferred approach.  I think it might be better to switch the
> "python" calls to %{__python} than to get rid of the %{__python3} macros.

I don't see where python3 is forbidden. It should be only a matter of taste like %{__rm} or rm (the first was needed, when /usr/bin was not in $PATH, but not anymore).

When Jef wants to change that, he's free to do it :)

> > * There was a problem with "summary" in the top line.
> 
> I'm afraid I can't find the problem you're referring to.

After applying your patch there was:
%else
Summary:
%endif

-> Summary was not always defined, but now is.

> 
> > When the tests pass, I think it's ok to build it in rawhide and f16.
> > Andrew, thanks for testing on f16 :)
> 
> Glad I can help.

Thanks! :)

There are several "ResourceWarning: unclosed file", where I'm unsure, if they'll cause problems.

This passes in f17:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3321972

Here are the ResourceWarning from above:
http://koji.fedoraproject.org/koji/getfile?taskID=3321973&name=build.log

When you are sure, they are harmless, I'll go ahead and build it in f16 and f17, unless there is a objection of another (co-)maintainer.

SPEC: http://tomspur.fedorapeople.org/scipy.spec
DIFF: http://tomspur.fedorapeople.org/scipy-diff2master

(In reply to comment #6)
> 
> I don't see where python3 is forbidden. It should be only a matter of taste
> like %{__rm} or rm (the first was needed, when /usr/bin was not in $PATH, but
> not anymore).
> 
> When Jef wants to change that, he's free to do it :)

Fair enough. :)

> After applying your patch there was:
> %else
> Summary:
> %endif
> 
> -> Summary was not always defined, but now is.

The file I created the patch from doesn't have that problem, so I have no idea how that happened. Anyway, I'm glad you noticed it and it's fixed.


> There are several "ResourceWarning: unclosed file", where I'm unsure, if
> they'll cause problems.
> 
> This passes in f17:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=3321972
> 
> Here are the ResourceWarning from above:
> http://koji.fedoraproject.org/koji/getfile?taskID=3321973&name=build.log
>
> When you are sure, they are harmless, I'll go ahead and build it in f16 and
> f17, unless there is a objection of another (co-)maintainer.

This seems to be a known problem with Scipy on Python 3.2. Scipy ticket #1385 has a comment saying that the warning is harmless, but it also has a patch: 

http://projects.scipy.org/scipy/ticket/1385

I suppose the two options are to ignore the warnings or to apply the patch.

(In reply to comment #7)
> 
> I suppose the two options are to ignore the warnings or to apply the patch.

By the way, my vote is to apply the patch, but I don't have strong feelings.

(In reply to comment #7)
> (In reply to comment #6)
> > Here are the ResourceWarning from above:
> > http://koji.fedoraproject.org/koji/getfile?taskID=3321973&name=build.log
> >
> > When you are sure, they are harmless, I'll go ahead and build it in f16 and
> > f17, unless there is a objection of another (co-)maintainer.
> 
> This seems to be a known problem with Scipy on Python 3.2. Scipy ticket #1385
> has a comment saying that the warning is harmless, but it also has a patch: 
> 
> http://projects.scipy.org/scipy/ticket/1385
> 
> I suppose the two options are to ignore the warnings or to apply the patch.

Thanks for the link.

The patch is already in 0.9, the ResourceWarnings are in nose, python3 but also some forgotten scipy files.

Will have a look soon.

Just pinging to see if you've had a chance to look at this or if you need any help.  By the way, it's not too late to get the package into Fedora 16, is it?  If it's in Fedora 16, I think I can get a bunch of people and stuff permanently moved over to Python 3, which would be great. :)

(In reply to comment #10)
> Just pinging to see if you've had a chance to look at this or if you need any
> help.  By the way, it's not too late to get the package into Fedora 16, is it? 
> If it's in Fedora 16, I think I can get a bunch of people and stuff permanently
> moved over to Python 3, which would be great. :)

Yep, I think ResourceWarnings are ignorable and according to the python3 doc they should be disabled by default (but somewhere the warnings seem to be turned on).

I reported it to your scipy ticket above and that should be enought to get it fixed in a next release.

I plan to build & update it in devel and f16, just wanted to let co-maintainers a change to object, like already said in comment #6.

It's not to late for f16 ;)

(In reply to comment #11)
> 
> Yep, I think ResourceWarnings are ignorable and according to the python3 doc
> they should be disabled by default (but somewhere the warnings seem to be
> turned on).

I think this is just during the scipy.test in the %check section.


> I plan to build & update it in devel and f16, just wanted to let co-maintainers
> a change to object, like already said in comment #6.

So far it's been pretty quiet. :)


> It's not to late for f16 ;)

Great.  Thanks again for all of your help with this.

(In reply to comment #12)
> > It's not to late for f16 ;)
> 
> Great.  Thanks again for all of your help with this.

You're welcome, happy testing and converting to python3 :)

scipy-0.9.0-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/scipy-0.9.0-2.fc16

Package scipy-0.9.0-2.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing scipy-0.9.0-2.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/scipy-0.9.0-2.fc16
then log in and leave karma (feedback).

scipy-0.9.0-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.