Adriane Boyd

#4467 adds the `debug-data` warning.

Hmm, the only other option I can think of is to normalize the patterns before checking them. I think it should be possible? You'd have to watch out for custom...

I tried this out starting in a clean venv. This project will need `requirements.txt` that includes the right version of `spacy-experimental` (you could just initially point to the right `git+https`...

The spacy version should go in `spacy_version` in `project.yml` instead?

There's some renaming missing for `span_predictor` in terms of the configs and output directories (`assemble` fails). If I rename enough to assemble, then: ``` ==================================== eval ==================================== Running command: /tmp/venv38-1/bin/python3.8...

Sofie probably wants to weigh in on this in general. I'm not sure why the CI isn't triggered, though? Let me try closing and reopening...

The underlying reason is that I made a change in spacy v3.2.0 that broke the compatibility (which I shouldn't have), so if you get spacy v3.1 and `spacy-experimental` than you...

I meant `uninstall`, sorry.

This is looking pretty good! I like that fact that it's now just one script to maintain.

I don't think we've decided for sure what to do here. This shows how a good plan for how we could manage the requirements for our CI/tests to make sure...