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 'e5648eb469'
${ noResults }
GPT3Discord/pyproject.toml

88 lines
1.7 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",
Added gpt-index commands
2 years ago
"gpt-index",
Update filetypes
2 years ago
"PyPDF2",
Support youtube videos
2 years ago
"youtube_transcript_api",
csv, powerpoint, image, mp3 support
2 years ago
"sentencepiece",
"protobuf",
"python-pptx",
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
]
csv, powerpoint, image, mp3 support
2 years ago
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"]
Remove extra envs from dockerfile Add missing ffmpeg to docker image Change compose to use the .env file Remove old docker workflow Set arm64 to only be added to release docker images Push to main and pr's make amd64 docker images only Update INSTALLATION.md Add more variables to sample.env Update requirements.txt to include whisper as a pypi package Update pyproject.toml with optional dependencies as [full] Make two docker images, base(865MB) and full(1.69GB) Add two requirements files as base and full for dependencies Base doesn't have image, video and audio indexing capability
2 years ago
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
[project.scripts]
gpt3discord = "gpt3discord:init"
Remove extra envs from dockerfile Add missing ffmpeg to docker image Change compose to use the .env file Remove old docker workflow Set arm64 to only be added to release docker images Push to main and pr's make amd64 docker images only Update INSTALLATION.md Add more variables to sample.env Update requirements.txt to include whisper as a pypi package Update pyproject.toml with optional dependencies as [full] Make two docker images, base(865MB) and full(1.69GB) Add two requirements files as base and full for dependencies Base doesn't have image, video and audio indexing capability
2 years ago
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
[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"
Remove extra envs from dockerfile Add missing ffmpeg to docker image Change compose to use the .env file Remove old docker workflow Set arm64 to only be added to release docker images Push to main and pr's make amd64 docker images only Update INSTALLATION.md Add more variables to sample.env Update requirements.txt to include whisper as a pypi package Update pyproject.toml with optional dependencies as [full] Make two docker images, base(865MB) and full(1.69GB) Add two requirements files as base and full for dependencies Base doesn't have image, video and audio indexing capability
2 years ago
[project.optional-dependencies]
full = [
"torch==1.9.1",
"torchvision==1.10.1",
"tokenizers==0.10.3",
"tqdm==4.64.1",
"numpy==1.24.2",
"scipy==1.10.1",
"nltk==3.8.1",
"huggingface-hub==0.12.1",
"more-itertools==9.0.0",
"ffmpeg-python==0.2.0",
"sentence-transformers==2.2.2",
"openai-whisper",
]
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.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"]