Bug: No link to new docs from this repo?

[nedbat]

Describe the bug

Pull request #822 created a nice-looking docs site. But coming to this repo, I see links to the now almost-empty old docs: https://testcontainers-python.readthedocs.io/en/latest/

Shouldn't we be sending people to the new docs?

I see python.testcontainers.org isn't live yet. I used to be able to see a list of containers: https://testcontainers-python.readthedocs.io/en/testcontainers-v4.2.0/

Now I don't see them: https://testcontainers-python.readthedocs.io/en/testcontainers-v4.12.0/modules/index.html

[alexanderankin]

i dont believe the new docs are live. moreover, I havent even reviewed them. i am trying to release the next release this week, i just need to make sure i have a free morning to field any issues or questions that come up. for some reason people seem to install the new version right away.

…

On Mon, Sep 8, 2025 at 1:49 PM Ned Batchelder ***@***.***> wrote: *nedbat* created an issue (testcontainers/testcontainers-python#869) <#869> *Describe the bug* Pull request #822 <#822> created a nice-looking docs site. But coming to this repo, I see links to the now almost-empty old docs: https://testcontainers-python.readthedocs.io/en/latest/ Shouldn't we be sending people to the new docs? — Reply to this email directly, view it on GitHub <#869>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACECGJHC74TUQX52XH4MRC33RW6S3AVCNFSM6AAAAACF6GNTOSVHI2DSMVQWIX3LMV43ASLTON2WKOZTGM4TKMBZHA4DSOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[alexanderankin]

after that i can try to review docs. i believe some intervention is needed from the core team (which i am not a part of) for making them fully live but im not sure we are there yet anyway

…

On Mon, Sep 8, 2025 at 2:16 PM David Ankin ***@***.***> wrote: i dont believe the new docs are live. moreover, I havent even reviewed them. i am trying to release the next release this week, i just need to make sure i have a free morning to field any issues or questions that come up. for some reason people seem to install the new version right away. On Mon, Sep 8, 2025 at 1:49 PM Ned Batchelder ***@***.***> wrote: > *nedbat* created an issue (testcontainers/testcontainers-python#869) > <#869> > > *Describe the bug* > > Pull request #822 > <#822> > created a nice-looking docs site. But coming to this repo, I see links to > the now almost-empty old docs: > https://testcontainers-python.readthedocs.io/en/latest/ > > Shouldn't we be sending people to the new docs? > > — > Reply to this email directly, view it on GitHub > <#869>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACECGJHC74TUQX52XH4MRC33RW6S3AVCNFSM6AAAAACF6GNTOSVHI2DSMVQWIX3LMV43ASLTON2WKOZTGM4TKMBZHA4DSOI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[nedbat]

I misunderstood, because the pull request was merged a few months ago. Maybe the real problem is that the old docs are gone?

[alexanderankin]

the old docs are currently in a broken state - readthedocs only supports pip and pip is not workable for complicated repo setups like this so we moved to poetry - i guess now people are suggesting we move to uv, so poetry "winning" seems to not have happened the way i had hoped. so that is where we are now.

honestly if the docs were the issue, i would just make markdown files in a docs folder in the repo that people could read but there are bigger issues with the library, like the whole API being different and being architected differently (which is not so easy to just reverse engineer because the python docker client differs, it appeared to me the last time i tried to do a major overhaul, from the other language drivers)

do you have questions that the docs should have answered? I'm happy to help (and highlight what should be made more visible in some documentation somewhere)

[alexanderankin]

btw the new list is here https://testcontainers-python.readthedocs.io/en/latest/modules/index.html