ryanmcgrath / twython

Actively maintained, pure Python wrapper for the Twitter API. Supports both normal and streaming Twitter APIs.
http://stackoverflow.com/questions/tagged/twython
MIT License
1.85k stars 397 forks source link

Remove nose-cov dependency? #553

Closed ppfeister closed 1 month ago

ppfeister commented 1 month ago

Hey Ryan

So, this package is a dependency of a dependency of a dependency of a dependency of a package I'm preparing for distribution on Fedora and Enterprise Linux.

nose-cov, as a package, has been dead for far loner than twython. When looking at the source, I don't see that package being used anywhere. Is it being used as a dependency of one of your dependencies? Is this something that we would be able to safely remove from the requires?

ppfeister commented 1 month ago

It's in the travis.yaml -- disregard

ryanmcgrath commented 1 month ago

…what thing are you packaging that depends on this?

I guess it could be removed if it’s a formality - if it’s there it’s probably a decade or so old and I’d have no context beyond that lol

On Sun, Aug 11, 2024 at 22:27, Paul Pfeister @.***(mailto:On Sun, Aug 11, 2024 at 22:27, Paul Pfeister < wrote:

Hey @.***(https://github.com/ryanmcgrath)

So, this package is a dependency of a dependency of a dependency of a dependency of a package I'm preparing for distribution on Fedora and Enterprise Linux.

nose-cov, as a package, has been dead for far loner than twython. When looking at the source, I don't see that package being imported anywhere. Is it being used as a dependency of one of your dependencies? Is this something that we would be able to safely remove from the requires?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

ppfeister commented 1 month ago

I have an ongoing project that will likely require TextBlob, whose only dependency is nltk, who then requires twython. One layer less than I thought on this chain but /shrug/

If we're not sure how removal will impact things, then it's probably easier for me to adopt the orphaned package on Fedora and bring it back to life

Preparing the dependency coveralls for distrib now, for a similar reason -- doesn't seem as sure of a thing to remove