release-monitoring for python projects

Dear python devel, While I was considering packaging of tmuxp tool, I noticed that dependencies of this package provided by Fedora are bit old. Eg. python-libtmux is 2 years old, which is old enough to prevent packaging any reasonable recent version of tmuxp. Do I read this right that we need to update both python-libtmux and other libraries in rawhide first so that review request for tmuxp can be created, and when it will be completed, the new package will land only in rawhide? I checked release-monitoring.org tool and noticed that wrong backed is selected for both packages. When I fixed this, the tool created "new version is available" bugs for both packages. Considering the information (most?) python packages have in it's spec file, would it make sense to preconfigure monitoring details based on information from the spec file when the package is added or updated? Or maybe just mandate that the release monitoring information are correct (and that the integration works) during review request? Or was there some bulk change some time ago related which could break this? -- Martin Bukatovič