Rafael AudibertandGitHub
f1dc4d7391
* chore: Migrate releases to `sampo` This is much closer to what we have in `posthog-js`, let's see if it's a good thing! There's still a lot to do before deploying this: - updating CI - updating README with instructions * Add sampo changeset * chore: Update to relase Python via Slack + sampo * Update release.yml * fix: Use pyproject.toml version as source of truth
655 B
655 B
posthoganalytics
Do not use this package. Use
posthoginstead.
pip install posthog
This package exists solely for internal use by posthog/posthog to avoid import conflicts with the local posthog package in that repository. It is an automatically generated mirror of posthog — same code, same versions, just published under a different name.
If you are not working on the PostHog main repository, you should never need this package. All documentation, issues, and development happen in posthog-python.