-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Add instructions for getting AllenNLP to run on Windows #612
Comments
+1 for windows support. |
+1 for windows! |
@matt-gardner : updated my allennlp install using |
@kearnsw this is a version issue, I just experienced the same thing myself. You need |
(you'll also need to uninstall all the other tensorboard distributions you installed, probably, because of namespace clashes etc.) |
+1 for windows |
+1 for windows |
+1 for Windows |
2 similar comments
+1 for Windows |
+1 for Windows |
+1 for windows |
+1 for windows support |
This should hopefully be easier now that PyTorch 0.4 officially supports windows. But SpaCy is still an issue, I think (although last I heard, they were working on it)... |
now that #1232 is in , things should be a lot easier in this regard since most, if not all, paths should be platform-invariant. Perhaps it's time to set up some windows CI and see what goes wrong? |
@nelson-liu, we should probably wait until the pytorch 0.4 PR is merged next week, at least. And I don't know how to set up a windows CI. Any ideas? |
Yeah, sorry --- definitely wait until #1126 is in. I'm not too sure where the CI configuration lives these days since the switch was made to teamcity, but it should be as "simple" as just setting up a new dockerfile running some variant of windows? Or we could go back to the open-source route and use appveyor |
+1 for Windows Also...it's not completely clear that it doesn't work with Windows in the main page...took me half a day to figure it out hahah |
+1 for windows. |
Note that jsonnet pip install isn't currently working with windows google/jsonnet#476 , which is another blocker towards support...maybe it'd be worth falling back to json in the event of jsonnet being unavailable? We'd need something that strips out json-incompatible stuff in the config fixtures, though, like the comments. That should be pretty easy, though... also looks like spacy linking fails when you don't have admin access on windows, so you can't do |
+1 for windows, resource module doesn't exist |
+1 for windows.. jsonnet cannot be installed using pipT_T |
+1 for windows! |
@BramVanroy things should mostly work on Windows, although we don't support and test that environment. We're unlikely to prioritize getting AllenNLP working seamlessly on Windows because neither the core development team nor most close collaborators use Windows. That said--we would welcome instructions for how to get AllenNLP running on Windows or people sharing their experience on this thread. |
if people have specific examples of things that don't work on Windows, it's possible we can address those, but we don't really have the bandwidth to proactively make sure everything works. |
I am running Windows as my daily driver (1080TI), and Linux at work when I have no other choice, i.e. when libraries don't support Windows (K80, soon to be replaced). I definitely understand your standpoint, but as a user I think it is a shame that some of these supercool projects don't get the Windows-treatment. Again, I understand that this is not always feasible from a practical point of view. I have only used ELMo, so my eperience with AllenNLP is limited. Installing is as straightforward as it is with Linux I suppose:
|
allennlp 0.7.0 is not working in windows python 3.6 torch 0.4.1 is working for me Error:
Anyone help me please |
You have to install a valid version of pytorch for your platform prior to installing allennlp. See the pytorch getting started web page. |
I required pytorch==0.4.1 and allennl==0.7.0 |
|
Not sure why you posted this. But it's important to know that the installation of torch differs per set-up. See the website for more. |
+1 for windows. |
@kunkaweb It would help if you indicate what isn't working for you on Windows. |
+1 for windows. |
1 similar comment
+1 for windows. |
+1 for Windows! |
+1 for windows |
+1 for windows. |
+1 for windows |
1 similar comment
+1 for windows |
Create a virtual environement in python and just run the following command:
This worked for me on Windows. |
+1 for Windows |
I don't quite understand the installation issues that people are having and it is hard to debug when everyone is just commenting +1. The steps to install are relatively straightforward, you just have to install the PyTorch wheels separately because (depending on your set up), PyPi will not install fetch the right/wanted wheels for your environmnent if you just do
If you get warnings or errors about other libraries during the installation of allennlp, you should install those before installing allennlp, plausibly not through pip but via a dedicated method for Windows. |
+1 Windows. Specifically, my error is involving using the don't stop pretraining repo when trying to build domains using I'm unsure if this is a Windows issue or not, but any resolution here would be greatly appreciated. If the reproduction of don't stop pretraining can be done on Colab, please let me know. I would greatly appreciate it. |
@viking-sudo-rm reported that he was able to get AllenNLP working on Windows by installing jsonnetbin. |
Hi Peeps, I have found the solution for installing AllenNLP for windows. Please find the details of installation steps below: Requirement:
Incase you are installing different version of AllenNLP on windows machine then look for that particular version of allenlp then if you get an error pertaining to torch (ERROR: Could not find a version that satisfies the requirement torch<1.x.x,>=1.x.x) then look for the version of PyTorch on this website [https://pytorch.org/get-started/previous-versions/](Previous PyTorch version) |
It's currently a pain, apparently, and I'm not sure how much work we should do to support it (if you're reading this and want Windows support, add a comment please). But @OyvindTafjord was able to get it actually working by modifying some things:
Pip install of sanic failed (because a dependency, uvloop, is not available for Windows) [ got around it by remove serve from commands ]Downloading dataset from S3 failed, I think because of non-allowed double quotes in the filename (from the etag) [ got around it by removing etag part of filename]I'm going to mark this issue as very low priority, until we hear people actually asking for us to support this. For now, the instructions will just live in this issue.
The text was updated successfully, but these errors were encountered: