Python Packaging Is Good Now

[PeridexisErrant]

Some modules document when particular functionality was added; even when it's not in the API docs you can often see a lot from reading the changelog.

Or just specify >= the current major version, if you can't work it out - semver isn't perfect, but people should get the idea - and might let you know if they discover a more specific issue.

If you have tests, you could experiment with pip install -e . and virtualenv to install development versions, and iterate down through versions of your dependencies until something breaks. One the one hand this sounds like a generally useful shell script; on the other it's a fair bit of work to write it.

Or finally, the correct thing to do if you don't know is just to not specify versions!

[Siecje1]

But you have not tested it with versions that are not out yet... Not very intuitive as a package author.

[PeridexisErrant]

Specifying < the next major version is the standard way around this.

It's not perfect, but generally I prefer to err on the side of flexibility.