On 6/10/24 23:43, Paul Pfeister wrote:
When building the rpm, I named the (rpm) package sherlock-project to have parity with PyPI, due to the same conflicting package. The importable module is still simply sherlock, however, which is _less than ideal_, and should probably be addressed.

With this discussion now being had on the deb side, I just introduced the conversation about renaming last night.

Still up for debate, but assuming we do decide to change it, we'll most likely use sherlock_project (again, for parity). I don't like the underscore, but it's the least likely to have conflict. I'll let you guys know of the decision.

(executable would remain sherlock even if the package name changes)

Hi!

Am I right, reading this, to double-guess you're also upstream author for sherlock (the social media package)? If so, why don't you simply change your module name to sherlock-project indeed? That would solve the conflict. So I'm all for it. Please make it happen.

Also, having module-name == pypi name == egg-name is a good practice.

Cheers,

Thomas Goirand (zigo)

Reply via email to