You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am updating the pkgsrc pkg for py-proj to 3.7.0. I do not have a clear memory of running tests before. In pkgsrc we invoked tests as 'make test' from the package directory, which invokes tests in a build-system-specific way in the build directory. This generally works, and it works with py-test which is normal.
Many packages load resources from the system rather than the build directory, making them not testable before install. As I generally don't try to fix those things, my normal practice is to install the new bits first and then test, so that test code that loads pyproj from /usr/pkg/lib/python3.12/site-packages/pyproj instead of the build dir will run as expected.
Then, I ran tests, and it failed to find _context. But, running the test program itself produced no errors, and I do see _context.so in the site-lib dir. ldd shows all its libs resolve ok.
Maybe it is trying to use the build tree? My build tree has _context.so and it looks normal:
$ pytest-3.12
ImportError while loading conftest '/tmp/work/geography/py-proj/work/pyproj-3.7.0/test/conftest.py'.
test/conftest.py:10: in <module>
import pyproj
pyproj/__init__.py:34: in <module>
import pyproj.network
pyproj/network.py:10: in <module>
from pyproj._context import _set_context_ca_bundle_path
E ModuleNotFoundError: No module named 'pyproj._context'
$ python3.12 test/conftest.py
Problem description
I am updating the pkgsrc pkg for py-proj to 3.7.0. I do not have a clear memory of running tests before. In pkgsrc we invoked tests as 'make test' from the package directory, which invokes tests in a build-system-specific way in the build directory. This generally works, and it works with py-test which is normal.
Many packages load resources from the system rather than the build directory, making them not testable before install. As I generally don't try to fix those things, my normal practice is to install the new bits first and then test, so that test code that loads pyproj from /usr/pkg/lib/python3.12/site-packages/pyproj instead of the build dir will run as expected.
Then, I ran tests, and it failed to find _context. But, running the test program itself produced no errors, and I do see _context.so in the site-lib dir. ldd shows all its libs resolve ok.
Maybe it is trying to use the build tree? My build tree has _context.so and it looks normal:
Environment Information
The text was updated successfully, but these errors were encountered: