For a proposed nose successor, pynose doesn’t seem to have gained much
community traction so far: it has seven stars on GitHub[1] (compared to
770 for nose2, which itself was never that widely adopted and has fewer
than ten dependent packages in Fedora); and the imperfect but fairly
useful reverse dependency index at Wheelodex[2] shows only three
packages that explicitly depend on it.
As far as I can tell, pynose exists because SeleniumBase[3] found it
easier to fork nose than to port away from it. I’m *definitely* not
saying we should only package things with a bunch of GitHub stars, but I
do have some concerns about whether or not pynose is going to remain a
generally-useful project in the medium-to-long term.
[1] https://github.com/mdmintz/pynose/stargazers
[2] https://www.wheelodex.org/projects/pynose/rdepends/
[3] https://github.com/seleniumbase/SeleniumBase
On 4/11/24 9:17 AM, Miro Hrončok wrote:
On 11. 04. 24 15:05, Sandro wrote:
On 11-04-2024 13:54, Miro Hrončok wrote:
On 11. 04. 24 11:55, Sandro wrote:
While I ponder those thoughts some more, moving forward in either
direction, the next step would be writing a change proposal?
I'd start by:
Packaging pynose without hacks (only making it Conflict with nose,
no compatibility Provides, Obsoletes or dist-infos).
That way, pro-active packagers can switch already.
That makes sense. Review is up [1]. If enough packagers adapt, I may
not need to go through the changes process.
And the change proposal can then describe what will be *added* to
pynose, rather than describing the approach from scratch.
Since predicting the future is difficult, I'll start on writing up a
proposal while the package is being introduced, anyway.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2274514
I see "# Package doesn't provide any tests" in the %check section.
That certainly feels a bit dodgy. This successor of a test framework
decided to ditch all of the tests it used to have? That is certainly a
red flag.
--
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
