Repository: pykeen/pykeen
Issue: RuntimeError: Datasets have been loaded with entrypoints since PyKEEN v1.0.5, which is now a very old version of PyKEEN
Root cause: Environment Incompatibility

### Describe the bug

I started exploring pykeen, and after installing pykeen and tried out the sample code provided in quickstart, I get below  error
```
RuntimeError: Datasets have been loaded with entrypoints since PyKEEN v1.0.5, which is now a
very old version of PyKEEN.

If you simply use `python3 -m pip install --upgrade pykeen`, the entrypoints will
not be reloaded. Instead, please reinstall PyKEEN using the following commands:

$ python3 -m pip uninstall pykeen
$ python3 -m pip install pykeen

If you are on Kaggle or Google Colab, please follow these instructions:
https://pykeen.readthedocs.io/en/stable/installation.html#google-colab-and-kaggle-users

If issues with Kaggle or Colab persist, please join the conversation at
https://github.com/pykeen/pykeen/issues/373```
```

### Expected behavior
started exploring this library, but stuck at the sample provided in the quick start, hence doesnt know the expected behavior

### How to reproduce

1) Create a new conda env and Install pykeen - pip install pykeen
2) copy the code from the quickstart and paste into a jupyter notebook cell and run it
```python
from pykeen.pipeline import pipeline

result = pipeline(
    model='TransE',
    dataset='nations',
)
```
3) uninstall and reinstall pykeen
```console
pip uninstall pykeen
pip install pykeen
```
4) Repeat step 2

### Environment

```console
python -m pykeen version 
```
output:
       
| Key             | Value                    |
|-----------------|--------------------------|
| OS              | nt                       |
| Platform        | Windows                  |
| Release         | 10                       |
| Time            | Thu Feb 17 23:35:05 2022 |
| Python          | 3.8.12                   |
| PyKEEN          | 1.7.0                    |
| PyKEEN Hash     | UNHASHED                 |
| PyKEEN Branch   |                          |
| PyTorch         | 1.10.2                   |
| CUDA Available? | false                    |
| CUDA Version    | N/A                      |
| cuDNN Version   | N/A                      |

### Additional information

Environment: Conda

```console
conda info
```
output:
```
         conda version : 4.10.3
    conda-build version : 3.21.6
         python version : 3.9.7.final.0
       virtual packages : __win=0=0
                          __archspec=1=x86_64
```

```console
pip show pykeen
```

output:
```
Name: pykeen
Version: 1.7.0
Summary: A package for training and evaluating multimodal knowledge graph embeddings
Home-page: https://github.com/pykeen/pykeen
Author: "Mehdi Ali, Max Berrendorf, Charles Tapley Hoyt, Laurent Vermue"
Author-email: pykeen2019@gmail.com
License: MIT
Location: c:\users\yhareen.tej\.conda\envs\pykeen\lib\site-packages
Requires: more-click, docdata, numpy, pyyaml, tqdm, pandas, tabulate, scipy, optuna, class-resolver, more-itertools, rexmex, pystow, click-default-group, dataclasses-json, sklearn, requests, click
Required-by:
```

Nobody on the pykeen team is using windows nor conda so we probably won’t be able to give much help with your setup. Have you tried using the direct windows installation instructions?

> Nobody on the pykeen team is using windows nor conda so we probably won’t be able to give much help with your setup. Have you tried using the direct windows installation instructions?

Yes it's working in dev mode, when i tried using direct windows installation

So the issue is with only with conda?

I am pretty sure this is related to using jupyter notebook, and is not caused by windows or conda.

I have recently played around with pykeen on colab where this error shows up quite often. 


I have an idea on how to update the class-resolver to address this (once and for all): https://github.com/cthoyt/class-resolver/issues/35

Hi @hareentej2 this should be fixed with #832. It’ll make it into pykeen v1.8.0 which we’ll release as soon as we figure out the recent performance regression, or you can install from GitHub 

@cthoyt I have used pykeen on WSL(windows subsystem for linux) which didn't give any issues. However in our POC(proof of concept), it didn't solve our requirement or maybe we still havent figure out the power of graphs. But, Thanks alot for making the fix into the next release and it is a good learning curve

I’m not familiar with the acronyms WSL or POC in this context. Could you please update your comment with them expanded in full