apadua/common/: apadata-0.2.5 metadata and description

Homepage Simple index Newer version available

Apadata is apadua's data science library

author	Nik Atlas
author_email	nikatlas@gmail.com
classifiers	Development Status :: 3 - Alpha Intended Audience :: Developers License :: OSI Approved :: MIT License Operating System :: OS Independent Programming Language :: Python :: 3 Programming Language :: Python :: 3.9 Programming Language :: Python :: 3.10 Programming Language :: Python :: 3.11 Programming Language :: Python :: 3.8 Topic :: Software Development :: Libraries :: Python Modules
description_content_type	text/markdown
license	MIT
project_urls	Repository, https://github.com/apadua-org/apadata
requires_dist	babel (>=2.12.1,<3.0.0) deep-translator (>=1.11.4,<2.0.0) django (>=3.0.0,<5.0.0) django-postgres-extra (>=2.0.8,<3.0.0) django-redis (>=5.3.0,<6.0.0) django-rq (>=2.8.0,<3.0.0) elasticsearch (>=8.0.0,<9.0.0) geostring (>=1.0.9,<2.0.0) goslate (>=1.5.4,<2.0.0) langdetect (>=1.0.8,<2.0.0) lxml (>=4.9.3,<5.0.0) openai (>=0.27.9,<0.28.0) openpyxl (>=3.1.2,<4.0.0) pyspellchecker (>=0.7.2,<0.8.0) pytest-snapshot (>=0.9.0,<0.10.0) redis (>3.0.0) rq (>=1.4.3) sentence-transformers (>=2.2.2,<3.0.0) sentry-sdk (>1.0.0) snapshot (>=0.1.2,<0.2.0) spacy (>=3.6.0,<4.0.0) spacy-transformers (>=1.2.0,<2.0.0) structlog (>=23.1.0,<24.0.0) textstat (>=0.7.3,<0.8.0) timeout-decorator (>=0.5.0,<0.6.0) tldextract (>=2.2.2) translate (>=3.6.1,<4.0.0) wikipedia (>=1.4.0,<2.0.0) wordfreq (>=3.0.3,<4.0.0)
requires_python	>=3.8.1,<4.0.0

File	Tox results	History
apadata-0.2.5-py3-none-any.whl Size 392 KB Type Python Wheel Python 3		Uploaded to apadua/common by apadua 2023-10-13 15:43:26
apadata-0.2.5.tar.gz Size 334 KB Type Source		Uploaded to apadua/common by apadua 2023-10-13 15:43:20

Apadata

The library that empowers apadua with AI! 🚀

Coverage Report

Very first steps

Setup your environment

If you have not already setup your environment according to the SETUP guide of apadua, please do so before proceeding.

Setup Guide

Initialize your code

If you don't have Poetry installed run:

make poetry-download

Make sure to add poetry to your PATH environment variable.
For MacOS:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zprofile

Initialize poetry and install pre-commit hooks:

make install
make pre-commit-install

Run the codestyle:

make codestyle

Poetry

Want to know more about Poetry? Check its documentation.

Details about Poetry

Poetry's commands are very intuitive and easy to learn, like:

poetry add numpy@latest
poetry run pytest
poetry publish --build

Building and releasing your package

Building a new version of the application contains steps:

Bump the version of your package poetry version <version>. You can pass the new version explicitly, or a rule such as major, minor, or patch. For more details, refer to the Semantic Versions standard.
Make a commit to GitHub.
Create a GitHub release.
And... publish 🙂 poetry publish --build

Articles:

GitHub Actions Documentation.
Maybe you would like to add gitmoji to commit names. This is really funny. 😄

🚀 Features

Development features

Supports for Python 3.8 and higher.
Poetry as the dependencies manager. See configuration in pyproject.toml and setup.cfg.
Automatic codestyle with black, isort and pyupgrade.
Ready-to-use pre-commit hooks with code-formatting.
Type checks with mypy; docstring checks with darglint; security checks with safety and bandit
Testing with pytest.
Ready-to-use .editorconfig, .dockerignore, and .gitignore. You don't have to worry about those things.

Deployment features

GitHub integration: issue and pr templates.
Github Actions with predefined build workflow as the default CI/CD.
Everything is already set up for security checks, codestyle checks, code formatting, testing, linting, docker builds, etc with Makefile. More details in makefile-usage.
Dockerfile for your package.
Always up-to-date dependencies with @dependabot. You will only enable it.
Automatic drafts of new releases with Release Drafter. You may see the list of labels in release-drafter.yml. Works perfectly with Semantic Versions specification.

Open source community features

Ready-to-use Pull Requests templates and several Issue templates.
Files such as: LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md are generated automatically.
Stale bot that closes abandoned issues after a period of inactivity. (You will only need to setup free plan). Configuration is here.
Semantic Versions specification with Release Drafter.

Makefile usage

Makefile contains a lot of functions for faster development.

1. Download and remove Poetry

To download and install Poetry run:

make poetry-download

To uninstall

make poetry-remove

2. Install all dependencies and pre-commit hooks

Install requirements:

make install

Pre-commit hooks coulb be installed after git init via

make pre-commit-install

3. Codestyle

Automatic formatting uses pyupgrade, isort and black.

make codestyle

# or use synonym
make formatting

Codestyle checks only, without rewriting files:

make check-codestyle

Note: check-codestyle uses isort, black and darglint library

Update all dev libraries to the latest version using one comand

make update-dev-deps

4. Code security

make check-safety

This command launches Poetry integrity checks as well as identifies security issues with Safety and Bandit.

make check-safety

5. Type checks

Run mypy static type checker

make mypy

6. Tests with coverage badges

Run pytest

make test

7. All linters

Of course there is a command to ~~rule~~ run all linters in one:

make lint

the same as:

make test && make check-codestyle && make mypy && make check-safety

8. Docker

make docker-build

which is equivalent to:

make docker-build VERSION=latest

Remove docker image with

make docker-remove

More information about docker.

9. Cleanup

Delete pycache files

make pycache-remove

Remove package build

make build-remove

Delete .DS_STORE files

make dsstore-remove

Remove .mypycache

make mypycache-remove

Or to remove all above run:

make cleanup

📈 Releases

You can see the list of available releases on the GitHub Releases page.

We follow Semantic Versions specification.

We use Release Drafter. As pull requests are merged, a draft release is kept up-to-date listing the changes, ready to publish when you’re ready. With the categories option, you can categorize pull requests in release notes using labels.

List of labels and corresponding titles

Label	Title in Releases
`enhancement`, `feature`	🚀 Features
`bug`, `refactoring`, `bugfix`, `fix`	🔧 Fixes & Refactoring
`build`, `ci`, `testing`	📦 Build System & CI/CD
`breaking`	💥 Breaking Changes
`documentation`	📝 Documentation
`dependencies`	⬆️ Dependencies updates

You can update it in release-drafter.yml.

GitHub creates the bug, enhancement, and documentation labels for you. Dependabot creates the dependencies label. Create the remaining labels on the Issues tab of your GitHub repository, when you need them.

devpi