Dependencies on PyPI needs to be updated.
See original GitHub issueMost users installs nltk
through:
$ pip install -U nltk
or
$ conda install nltk
but somehow the PyPI requirements seems to be far lacking behind the ones in pip-req.txt
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Dependency Management with Pip, Python's Package Manager
Updating one or more packages in a project can result in dependency conflicts since newer package versions will often require newer versions of ......
Read more >How to get PyPI to automatically install dependencies [duplicate]
To have pip install dependencies automatically, I include at the top of setup.py before setuptools.setup(): requirements = [] with ...
Read more >Specifying Dependencies — Python Packaging Tutorial
Sometimes you'll want to use packages that are properly arranged with setuptools, but aren't published to PyPI. In those cases, you can specify...
Read more >Dependency Resolution - pip documentation v22.3.1
pip is capable of determining and installing the dependencies of packages. The process of determining which version of a dependency to install is...
Read more >Managing Python Dependencies with Requirements.txt
This is normally done by using pip freeze > requirements.txt, which records an environment's current package list into requirements.txt. Since ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I like @kmike suggestion too, having something like:
and maybe:
and for lazy users:
On a related note, I think we need to also include the downloads in the
setup.py
code such that users won’t see an error when using “NLTK default” functions e.g. :Currently, now the users must download:
Adding all these packages to
install_requires
sounds like a maintenance nightmare - user must be able to build all these packages (many of them contain C/C++ extensions) in order to install NLTK - even if they are not needed at all for the user.I don’t see them as required dependencies, they are optional dependencies which enables some of NLTK features. Currently the only required dependency is six - a small pure Python module. There is no reason for users to build gensim if they only want to use nltk tokenizer.
Nose, tox, coverage and pylint (and a few other packages which are their transitive dependencies) are not NLTK dependencies, they are packages required to run NLTK tests. They are not needed for the end users.