Hey Python friends, I've got a packaging/dependency question.

A project I co-maintain has a dependency that a significant % of users require, so we'd like to include it by default. However it also causes the vast majority of all our installation problems. So we'd like to have a flag you can pass to the "pip install x" command, or an env variable the user can set, that skips that dependency.

It's okay if the workaround is finicky, debugging this dependency is 100x more finicky.

Any ideas?

Follow

@shauna not knowing what kind of problems that package is causing, it's hard to say, but I'd try to work with the maintainers of that package so it's more well-behaved.

If the maintainers aren't interested in that, you could consider forking...but that has a whole other set of problems. I've done it for small libraries, but the nature of your initial problem makes me think that's not your case.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.