2 Commits (f6eb74b8ebf0a80e9d25f5bb44f3e17a4572398a)

Author	SHA1	Message	Date
dependabot[bot]	4c3654654d	Bump actions/checkout from 2 to 3 ... Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/v2...v3) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>	2 years ago
Cooper Ry Lees	4677e91093	Add pyproject.toml for building / installing ... - Add a pyproject.toml to install all modules and packages - Use hatch to build + install - Still only claim support for 3.9 - We don't specify versions in pyproject.toml on purpose so people can have some flexibility there - If they want the tested pinned versions they can use requirements.txt like Docker + CI does ... - This will allow the package to be uploaded to PyPI if you'd like now :) - `git mv main.py gpt3discord.py` as main.py is to common (incase someone installs to shared python env) - Move initalization code into a init() function to have entry point script call - Update `Dockerfile` to install via pyproject.toml - Both docker + build CI install requirements.txt so we get the known versions of dependencies that work - Update README for less steps now in installing - Side note, we will have to track versions now and increment as we see fit - I'd like to discuss using GitHub releases here ... - Sort requirements.txt to be alphabetical ... Test: - Add python 3.9 CI to install our module - Paves the way to add more CI to help me test the module works in 3.11 - Build in a local venv - `python3.9 -m venv /tmp/foovenv` - `/tmp/foovenv/bin/pip install -r requirements.txt` - `/tmp/foovenv/bin/pip install .` - Build in docker - `docker build -t gpt3discord .`	2 years ago