open-source-mirrors
/
GPT3Discord
mirror of https://github.com/Kav-K/GPT3Discord
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '50e6f59ab5'
${ noResults }
GPT3Discord/pyproject.toml

62 lines
1.3 KiB
Raw Normal View History Unescape

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
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
[project]
name = "gpt3discord"
description = "A Chat GPT Discord bot"
readme = "README.md"
requires-python = ">=3.9"
license = "MIT"
keywords = []
authors = [
{ name = "Kaveen Kumarasinghe", email = "contact@kaveenk.com" },
]
classifiers = [
"Development Status :: 4 - Beta",
"Programming Language :: Python",
"Programming Language :: Python :: 3.9",
]
dependencies = [
"Pillow",
"py-cord",
"python-dotenv",
"requests",
"transformers",
Make recurring file operations all async, add custom opener file feature
2 years ago
"pycord-multicog",
Update pyproject.toml Signed-off-by: Kaveen Kumarasinghe <k5kumara@uwaterloo.ca>
2 years ago
"aiofiles",
Multi tenancy api key support
2 years ago
"pinecone-client",
"sqlitedict",
Add missing requirements
2 years ago
"backoff",
health check service
2 years ago
"flask",
update requirements
2 years ago
"flask",
"beautifulsoup4",
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
]
dynamic = ["version"]
[project.scripts]
gpt3discord = "gpt3discord:init"
[project.urls]
Documentation = "https://github.com/Kav-K/GPT3Discord/#readme"
Issues = "https://github.com/Kav-K/GPT3Discord/issues"
Source = "https://github.com/Kav-K/GPT3Discord"
[tool.hatch.version]
path = "gpt3discord.py"
[tool.hatch.build]
include = [
"cogs/*.py",
"models/*.py",
Fix pyproject
2 years ago
"services/*.py",
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
"gpt3discord.py",
]
#[tool.hatch.build.targets.sdist]
Update readme and sample.env Small change to text service
2 years ago
#packages = ["cogs", "gpt3discord.py", "models", "services"]
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
#[tool.hatch.build.targets.wheel]
Update readme and sample.env Small change to text service
2 years ago
#packages = ["cogs", "gpt3discord.py", "models", "services"]
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
[[tool.hatch.envs.test.matrix]]
Update pyproject.toml Signed-off-by: Kaveen Kumarasinghe <k5kumara@uwaterloo.ca>
2 years ago
python = ["39"]