-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install of mkdocs fails with nltk 3.5 #2062
Comments
First of all, Second of all, looking at the attached log, it appears that the |
Hi Waylan, thanks for your reply. I understand that you point me to another dependency, but please follow my reasoning; |
All you need to do is There seems to be some complaint here about dependencies, but Material uses CI to build docs and it is having no issues. Also, I use mkdocs in CI and am having no issues. This ran today, 8 hours ago, using the latest mkdocs and mkdocs-material: https://github.com/facelessuser/pymdown-extensions/runs/587998198?check_suite_focus=true. No issues. |
@klaascuvelier nowhere do we declare However, as @facelessuser points out, no-one else seems to be experiencing the issue. And as I pointed out, your log seems to indicate the issue is with |
That's not true because we had the same problem. See: |
Perhaps I should stated that one one else has reported having the issue. In any event, thanks @froschdesign for providing a second report. However, again the issue is with |
Yes, with this commit nltk/nltk@6fbad04 for version 3.5: install_requires=[
"click",
"joblib",
"regex",
"tqdm",
], https://github.com/nltk/nltk/blob/6404712d0a64c3d6e3700032c23a59803615460c/setup.py#L103-L108
|
Ah, okay. I see to ways forward:
Actually, it would probably be best to report to both projects. I know I would want to receive the report if I was working on either. When we get some feedback about how they will move forward, that will inform us on how to proceed (do we require an older version or a newer version?) |
Hello @waylan, I add the same problems with our mkdocs build. It seems to me that it could be possible to have another solution waiting for upstream fixes. |
I do indeed think that would be a solution. I understand that it's not directly your library that's breaking something. But by using external libraries (that can break) you can't just point to them and wait for them to fix possible issues. |
☝️ created an MR to hardcode the dependency |
I just ran into this when preparing the latest release for |
Ah, it's an environment build issue for regex as it is built with C on Linux. I thought there were wheels for it? Maybe not for Linux I guess. |
Thank you @squidfunk for providing such a helpful report. Looking at the regex package, there are wheels (prebuilt files) for the following platforms:
For any other platform, the package will need to be compiled on installation. Turns out this is not a version issue at all. Sure, earlier versions of As For information on It appears that one solution is to ensure that the appropriate The other option is to install the Finally, for completeness, I should note that no MacOS wheels are provided. However, I just checked and it appears that
|
Just looked at yeraydiazdiaz/lunr.py and version 0.5.8 was just released which maintains compatibility with lunr.js 2.3.8, but also restricts its dependency to As our dependency on lunr.py is hard, we should simply update it to version |
Lunr.py version 0.5.8 maintains compatability with Lunr.js 2.3.8, but restricts its dependnecy to nltk>=3.2.5,<3.5, which avoids installation issues on some Docker images. Fixes mkdocs#2062.
Lunr.py version 0.5.8 maintains compatability with Lunr.js 2.3.8, but restricts its dependnecy to nltk>=3.2.5,<3.5, which avoids installation issues on some Docker images. Fixes #2062.
Hi,
First of all, thank you for mkdocs. We're using this in our company and are very happy to have it.
I noticed that the installation of mkdocs started failing for us yesterday. After some investigation I found out that the nltk lib had a version bump (3.5) yesterday and that's were it goes wrong.
I was able to use the previous nltk version (3.4.5) by adding it directly to our ci file
This solves the issue for us.
I am not really used to python and its ecosystem, so perhaps I am overseeing an actual "fix".
But if this is a really issue, I guess the
3.5
nltk version should be blacklisted from the install?Output of the error
The text was updated successfully, but these errors were encountered: