https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257073
--- Comment #9 from p5b2e9...@t-online.de --- While I'm absolute sure that all Python-Port-Maintainers internalized the whole https://wiki.freebsd.org/Python/PortsPolicy and beyond, I like to point the more casual readers (those looking for distraction and entertainment) to this: Use common sense for upstream version requirements that set maximum versions or pin very specific versions, eg: ==, <=, and more importantly to https://wiki.freebsd.org/Python/PortsPolicy#Upstreaming Python port maintainers SHOULD (strongly encouraged) aim to: * Craft port patches that are likely to be accepted upstream, even if they are committed locally first. * Create upstream issues for bug reports and enhancement requests. Eg: - Better documented requirements in install_requires, tests_require, setup_requires - Optional dependencies made a part of extras_require - Support for python setup.py test command (for regression testing) ... * Regularly test and report test suite failures of Python packages on FreeBSD. Python-(Upstream)-Dependencies have become more and more a wickerwork that should be addressed where it comes from. More communication with Python-upstream is needed because more and more Python-Environmentists are trying to survive in virtual environments, condas and the like, which results in a never-touch-again-mentality if got something to work at least for a while. -- You are receiving this mail because: You are on the CC list for the bug.
