Date: Sat, 27 Jul 2013 10:25:49 -0400 From: "John W. O'Brien" <john@saltant.com> To: edwin@FreeBSD.org Cc: freebsd-ports-bugs@FreeBSD.org, freebsd-python@FreeBSD.org Subject: Re: ports/180889: [MAINTAINER] math/py-pandas: Update to 0.12.0 Message-ID: <51F3D86D.6080808@saltant.com> In-Reply-To: <201307271320.r6RDK8hH047052@freefall.freebsd.org> References: <201307271320.r6RDK8hH047052@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] - test_banklist_url (pandas.io.tests.test_html.TestReadHtmlBase) - test_multiple_matches (pandas.io.tests.test_html.TestReadHtmlBase) - test_pythonxy_plugins_table (pandas.io.tests.test_html.TestReadHtmlBase) - test_spam_url (pandas.io.tests.test_html.TestReadHtmlBase) I suspect that the redports tests that generate errors where _parse() raises "ValueError: Invalid URL" are caused by failure of the underlying use of urllib2 to respect the HTTP_PROXY environment that redports uses. I tried wrapping the nosetests with env http_proxy=$HTTP_PROXY [...] with no effect. Suggestions are welcome. - test_pytables_native_read (pandas.io.tests.test_pytables.TestHDFStore) This is somewhat more concerning, but it may be a problem with the devel/py-tables soft dependency. - test_read_dta10 (pandas.io.tests.test_stata.StataTests) - test_stata_doc_examples (pandas.io.tests.test_stata.StataTests) - test_write_dta5 (pandas.io.tests.test_stata.StataTests) - test_write_dta6 (pandas.io.tests.test_stata.StataTests) These tests generate errors on my system when I run the suite from a non-privileged user account. Initial analysis indicates that the tests try to write to a file inside the test data directory (%%PYTHON_SITELIBDIR%%/%%PYEASYINSTALL_EGG%%/pandas/io/tests/data/), which is clearly bad behavior. I will report this upstream and supply any patch that results to this port. In the mean time, these are harmless errors. I will continue to investigate these test errors and supply additional patches as appropriate. Assistance of any kind is welcome. For the time being, I believe that the upgrade is in good shape to ship. Thank you, John [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJR89hxAAoJEBRzAKlhyP/FoicIAKb2LsZ10A2Xs65zwhskIbD9 O+t4JRXCIBGWskqCnivMpiqvk9MVRQnkVmrVrPYfG8/vg84lNAao1QEzUmfAcOe8 MiKGbIm/gWEptPO0KRaXbSFbWPKsAQuba76A/ApmioI7PhlomZ694codazUBzSyO nPpEebvOVI8uFjzwvOXC6MfDs85o/rAmzgiPXU7AsztJEj3nByXkTuTZjKhkbJ6q mQoaElTPGGz1pQldtt1dzAfFCiFKPVshHgAJwkAoYLSDKXfA8ZGJFHiOEWEshIcJ s4aTl3UAW8YaGupvzGpB3gGsrEm6+hc/fN7TlCWypFiZjtnJ6BxubVvXpj4dB40= =WWaF -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51F3D86D.6080808>