nltk
Here are 2,451 public repositories matching this topic...
-
Updated
Oct 1, 2020 - Jupyter Notebook
-
Updated
Jun 1, 2022 - Python
-
Updated
Mar 27, 2022 - Python
-
Updated
Dec 24, 2020 - Jupyter Notebook
-
Updated
May 16, 2022 - Python
-
Updated
Jun 1, 2021 - Python
-
Updated
Jul 5, 2022 - Python
-
Updated
Jan 17, 2019 - Jupyter Notebook
-
Updated
Jul 6, 2022 - Python
-
Updated
Jun 21, 2021 - Python
-
Updated
Jul 10, 2019 - Jupyter Notebook
-
Updated
Apr 22, 2020 - Python
-
Updated
Sep 14, 2020 - Jupyter Notebook
-
Updated
Nov 24, 2017
-
Updated
Dec 20, 2020 - Python
-
Updated
Sep 18, 2020 - Jupyter Notebook
Text version
0.9.1
Orange version
3.26.0.dev
Expected behavior
When sharing workflows with o
-
Updated
Nov 10, 2020 - Jupyter Notebook
-
Updated
Jul 6, 2022 - Python
-
Updated
Jun 5, 2020 - Jupyter Notebook
-
Updated
Jun 10, 2018 - Ruby
-
Updated
Jan 1, 2019 - Python
-
Updated
Jun 2, 2021 - Python
-
Updated
Aug 16, 2017 - Python
Improve this page
Add a description, image, and links to the nltk topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the nltk topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Checking the Python files in NLTK with "python -m doctest" reveals that many tests are failing. In many cases, the failures are just cosmetic discrepancies between the expected and the actual output, such as missing a blank line, or unescaped linebreaks. Other cases may be real bugs.
If these failures could be avoided, it would become possible to improve CI by running "python -m doctest" each t