Metadata-Version: 2.4
Name: rule-engine-core
Version: 0.1.1
Summary: A rule engine core library for Python.
Home-page: https://github.com/temp-noob/rule-engine
Author: Mohit Tripathi
Author-email: tripathimohit051@gmail.com
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.10
Description-Content-Type: text/markdown
Requires-Dist: psycopg2-binary
Dynamic: author
Dynamic: author-email
Dynamic: classifier
Dynamic: description
Dynamic: description-content-type
Dynamic: home-page
Dynamic: requires-dist
Dynamic: requires-python
Dynamic: summary

## Build
-> create venv and activate
(install meta)
-> pip install setuptools wheel twine
(build package)
-> python setup.py sdist bdist_wheel
-> pip install dist/rule-engine-core-0.1.0-py3-none-any.whl
(Publish to pypi)
-> pip install twine
-> twine upload dist/*

### Release order

Every service installs this package from PyPI, so a change here is invisible to them until
it's published. When a service needs new core API:

1. Bump `version` in `setup.py`.
2. Build and `twine upload`.
3. Then bump the `rule-engine-core>=<version>` floor in that service's `requirements.txt`
   and `pyproject.toml`.

Until step 2 lands, a service PR carrying a raised floor fails at `pip install` and its CI
goes red. That's the point — it's the reminder to publish, and it beats an `ImportError`
in prod. So publish before merging the consumer.

### Docker
-> `psql --username=$POSTGRES_USER -d $POSTGRES_DB`
