Date: Tue, 08 Aug 2017 10:35:45 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 221311] [NEW PORT] databases/influxdb-python: InfluxDB Python client Message-ID: <bug-221311-21822-cWMMaNOSxO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221311-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-221311-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221311 --- Comment #7 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Konstantin Shapkin from comment #4) As far as "ImportError: No module named tests" goes: a) there is no tests/ directory (module) in the root b) there *is* an influxdb/tests directory (module) c) their CI (travis.yml/tox.ini) configuration runs: 'nosetests -v ...' directly d) (c) means they don't test their "python setup.py test" test entry point My guess is that tests/ was probably moved to influxdb/tests at some point,= and setup.py:test_suite was not updated (to 'influxdb.tests') to match. Since n= ose has good test discovery, it finds influxdb/tests without being pointed to i= t. This all means, you can probably run tests by either: 1) Patching setup.py:test_suite, settings its value to 'influxdb.tests' 2) use ${PYTHON_CMD} -m nose as the test command Personally, I would do (1), as I prefer to use the canonical 'pythonX.Y setup.py test' command, making it work if I have to (with patches), and submitting the changes/bugfixes upstream so projects know that people care. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221311-21822-cWMMaNOSxO>