Random interval clicking is better than clicking away every second, but it still doesn't represent a "realistic" clicking style that a human would replicate if actually clicking and using the mouse for real-world activities.

I also recently watched a video about the Strategy pattern, and I think it would be a good idea to create different types of clicking patterns and styles to simulate a "real" human interaction with the mouse.

Making a system of my own dunder methods or abstract methods is simple enough, the tricky part is coming up with algorithms for different clicking patterns without massively duplicating code.

CONTRIBUTING.md, and probably other files too, are now outdated after recent updates.

Go through the repo and update any documents.

I heard something about pre-commits, that they're basically git hooks that can run tests, linters, formatters, and other things before a commit even happens.

This isn't high priority, but something tool to learn about.

It looks like there is a couple ways to manage packaging in the python ecosystem

• Pipenv
• Poery
• Flit
• pip-tools

I like pipenv when developing, but it's packaging a approach is lacking. I would still have to manually manage packages, and I would like to do as little as possible when it comes to packaging.

Poetry seems to handle packaging better by using pyproject.toml directly, but it's development workflow is lacking, and doesn't integrate with virtual environments as well as pipenv.

I need to add more developer information about setting all interpreters with pyenv, or maybe look into a plugin between tox and pyenv.

Remove information about "only supporting python 3.9." With tox, this package is now supporting python 3.6 - 3.9.

And preform general clean up, and find another changes that need to added / removed.

There's several poetry commands to create the dist folder, then publish to pypi. But how do I install my package to my local machine for testing?

Maybe I should try using pipx after publishing to pypi?

Tox looks like a testing automation tool, which can be used to test multiple python interpreters easily.

I'm already using pytest with poetry, and I'm only supporting python 3.9 right now. Do I want to use tox with this project?

Maybe, just for the hell of it?

The script to run coverage reports still relies on bash. How can I make this cross platform?

• Turn it into python script?
• logic to determine OS, and open appropriate shell?
• Just use bash, and make git a hard requirement?

Self explanatory. Read the Docs for poetry and pyproject.toml specs to figure out how to exclude files from being built and distributed.

Docstrings are probably out of date by now. I've changed the basic api at least 2 or 3 times now.

Go through all docstrings and make sure they are up-to-date, and be sure to add any execption examples, or gotcha's an end user would need to know.

Might need todo more research on docstring for exception examples, and better docstrings in general.