testcontainers / testcontainers/testcontainers-python
RFC: 4.x releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 386
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
Context
Now that we've got a release pipeline back in action, there is lots we can do to make things nicer.
I am raising this issue in order for community to gather and talk about what should be fixed as priorities and what improvements we want to add.
Known Issues
We know there are several areas we want to improve:
- We want to thin out dependencies where possible - prefer giving a ready container but not be biased on how you should connect to the container. Example: postgres containers enforcing SqlAclhemy, as seen in #445
- We want to improve package typing so people have better developer experiences, as seen in #305 and the PRs it spawned so far
- Adding new containers, as there is demand for it #439, #441, #389, etc
[!NOTE]
The list above is not conclusive, please comment on this issue and show your support!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the release pipeline context and the linked issues #445, #305, #439, #441, and #389. The issue is an open RFC rather than a scoped change; done would require agreeing on 4.x priorities and turning them into specific, actionable issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100