[Rpm-maint] [rpm-software-management/rpm] Python module's name changed unnecessarily, making it impossible to express dependencies on it (#373)

[Jeff Johnson]

@AdamWill: Please supply the actual failure mode. Yes Name: is different; it likely doesn't matter (but yes is a change, and is confusing).

Reading on egg-info, I find this statement:

(Note: the pkg_resources module does not automatically look for eggs on PyPI or download them from anywhere; any needed eggs must already be available in a directory on sys.path, or require() will raise a DependencyNotFound error. You can of course trap this error in your code and attempt to find the needed eggs on PyPI or elsewhere. If you want to automatically install dependencies for a project you're working on, you should probably build it using setuptools, which lets you declare dependencies where they can be found by tools like EasyInstall. Setuptools is also needed in order to build eggs.)

So the underlying dependency checking semantic appears to be a module directory on some Python load path.

What appears to be missing is the rpm-python directory (and a symlink may fix; please try.)

Adding 2 egg-info files with different Name: strings might work. Just as easily, you could certainly rewrite your dependencies between F26 -> F27, or just not express the dependency within setup tools; since you are not checking a version in your install.requires file, egg-info files are rather overkill.

*shrug*

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/373#issuecomment-353683579
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171222/14426e60/attachment.html>