MNT: fix circle

[jklymak]

No description provided.

[jimustafa]

I think the errors with circle are related to the python version being different from what was used when pinning the requirements. Given that the cheatsheets are more an "application" than a "library", the python version should probably be fixed. The requirements were originally generated with python 3.7.3, and it looks like python 3.9 was used in #83.

Can circle do something similar to gh actions (below), and specify the python version?

cheatsheets/.github/workflows/main.yaml

Lines 16 to 18 in 7ca0fd6

	- uses: actions/setup-python@v2
	with:
	python-version: 3.7

[jklymak]

I mean, I'm sure its probably possible. I wasn't planning to prioritize this, so maybe I'll move to draft. @jimustafa if you wanted to take over trying to get this to work, I'd be great with that. Otherwise, I'll try to circle back to it after 3.5.0 is released.

[jklymak]

(to be clear, my experience with CircleCI is copying other setups and googling - I'm not particularly knowledgeable!)

[jimustafa]

I can take a look at circle and try to get a config working. In the meantime, should we remove the circle config introduced in #83 to prevent the failed checks?

[jklymak]

I think so? It was just to bootstrap being able to turn circle on at the project level for this repo.

[jklymak]

I just made the circle test a placeholder from now. Not sure what happens if we remove it altogether and then merge, if we need to reenable at the project level

[jklymak]

I'll self merge this to unbreak the build. Note this is not user-facing...