Python package release tracking issue

[tombruijn]

Tracking issue for first and subsequent Python package releases.

To do

Stage 1: first alpha test release

• Add changelog file (no mono required yet)
• First release for Python package #3
• Implement missing configuration options #16
• Add Python versioning scheme mono#54
• Release to production Pypi registry #29
  • Blocked on desired package name, now available as "appsignal-beta".

Stage 2: Beta testers

• Add Python support mono#50
• Install command #18
• Include cacert.pem file #30
• Refactor config  #36
• https://github.com/appsignal/appsignal-docs/issues/1284
• Add internal logger #34
• Add Python to the AppSignal changelog #5 - small issue
• Validate Push API key in install command #42
  • Python related decision, Python package release tracking issue #14 (comment)
• Installer should offer to install relevant dependencies #43
• Backtraces are not detected as Python backtraces #72
• Ignore queries on boot #69
• Load file/initial config options source load #68
• https://github.com/appsignal/appsignal-docs/issues/1285
• https://github.com/appsignal/appsignal-server/issues/9532
• https://github.com/appsignal/appsignal-agent/issues/1004
• Internal testing

Stage 3: 1.0 release

• Add demo command #12
• Add diagnose command #19
• https://github.com/appsignal/appsignal-agent/issues/999
• Add to blog:
  • Add a Python category/tag?

Stage 4: Feature parity

• Implement metrics #7
• Support more Python instrumentations #13
• Support FreeBSD #49
• Implement logging #8
• Set _APPSIGNAL_PROCESS_NAME config #32

[tombruijn]

I think we should also decide on issue https://github.com/appsignal/integration-guide/issues/73 and update the Python package to match before we ship a first release–that's not a prerelease–to the production registry.

[backlog-helper]

• This issue has not had any activity in 14 days. Please provide a status update if it is still relevant. Closed it if it is no longer relevant. Or move it to another column if it's blocked or requires another look at it. - (More info)

---

This is a message from the daily scheduled checks.

New issue guide | Backlog management | Rules | Feedback

[tombruijn]

Closing this tracking issue. We're close to a 1.0 release. The remaining linked open issues can be picked up individually according to our cycle planning.