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

[Adam Williamson]

I'm definitely only talking about Python concepts here. C concepts don't play into all this *at all* since we're only talking about Python ecosystem stuff.

"If setup tools is constructing module paths from egg-info Name: directives (which is rather deficient)"

No, it's not doing that. There is no conceptual connection at any level between the name of the "built distribution" and any filesystem location or name you could pass to `import`. It's purely and simply an identifier for the "built distribution" itself. Just like the name of an RPM package is purely and simply the name of the package: it implies nothing whatsoever about the contents of the package (except by distribution policy).

It's all just like having an rpm package called 'bar' that requires an rpm package called 'foo'. Those are *just* package name identifiers, right? Nothing involved would assume that the rpm package called 'bar' includes a `/usr/bin/bar`, or a `libbar.so`, or a Python module called `bar`, or anything like that. It's just a *name*.

"If Name: is purely informative, then something like a symlink within site-packages might be a sufficient finesse."

This still seems to suggest you're misunderstanding something to me. There is no problem at all with the paths under site-packages, here. The actual site-packages files in RPM 4.13 and RPM 4.14 are all in *exactly the same place*. That's not the part that changed. The part that changed is the name of the "built distribution" - the name that is passed to the `setup()` method as the `name` argument, and that therefore appears in the `.egg-info` file. *That* is what changed. Nothing in the history of humanity has ever looked for anything under `site-packages/rpm-python/`, to be 100% clear, nor has anything ever been located there. That is absolutely not the problem here.

-- 
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-353698153
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171223/96654495/attachment.html>