Replace pkg_resources with importlib.resources

[Copilot]

Replaces deprecated pkg_resources API with standard library importlib.resources in add_py_module().

Changes

• codepy/libraries.py: Replaced pkg_resources.resource_filename() with importlib.resources.files()

# Before
from pkg_resources import Requirement, resource_filename
return resource_filename(Requirement.parse(name), f"{name}/include")

# After
from importlib.resources import files
return str(files(name) / "include")

Behavior is equivalent for all current usages (codepy, pyublas, hedge) where distribution name matches module name. Compatible with Python 3.10+ requirement (files() introduced in 3.9).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Replace pkg_resources</issue_title>
<issue_description>@copilot Replace the pkg_resources use with importlib.resources.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Replace pkg_resources #64

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

Updates add_py_module() to stop using deprecated pkg_resources and instead use the standard-library importlib.resources to locate a Python package’s bundled include/ directory for toolchain header search paths.

Changes:

• Replace pkg_resources.resource_filename() lookup with importlib.resources.files() for package include path resolution.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

importlib.resources.files() returns a Traversable that is not guaranteed to be a real filesystem path (e.g., zip/egg installs). Converting it to str and passing it as a compiler -I include dir can yield a non-existent path and break compilation, whereas pkg_resources.resource_filename() previously extracted resources to a real path. Consider resolving the package location via importlib.util.find_spec(...).submodule_search_locations (filesystem-only, like add_numpy) or materializing the directory with importlib.resources.as_file() and ensuring the extracted path remains valid for the entire build.

Suggested change

	from importlib.resources import files
	return str(files(name) / "include")
	from importlib.util import find_spec
	spec = find_spec(name)
	if spec is None:
	raise RuntimeError(f"Could not find module '{name}'")
	libdir = spec.submodule_search_locations
	assert libdir is not None
	from os.path import join
	return join(libdir[0], "include")