Should python3dist(...) provides generator fail when the version is = 0?

[Miro Hrončok]

Hello Pythonistas,

today, I've looked up packages in rawhide providing python3dist(...) = 0 and I 
opened bugzillas for them:

https://bugzilla.redhat.com/showdependencytree.cgi?id=python3dist0

While version 0 (or equal versions like 0.0 or 0.0.0) is probably technically 
valid, it most certainly indicates a packaging error (most likely but not 
necessarily a downstream packaging error).

Should we prevent this error from happening by explicitly erroring (and failing 
the build) when it happens? I think it would make the dependency generators 
more robust.

In an unlikely scenario when packagers actually want to package version 0, they 
can reach out and we can allow it via some configuration (but [YAGNI], so I 
don't want to clutter the generator with yet another option right away).

[YAGNI] https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it

[Petr Viktorin]

On 29. 01. 22 22:11, Miro Hrončok wrote:
> Hello Pythonistas,
>
> today, I've looked up packages in rawhide providing python3dist(...) = 0 
> and I opened bugzillas for them:
>
> https://bugzilla.redhat.com/showdependencytree.cgi?id=python3dist0
>
> While version 0 (or equal versions like 0.0 or 0.0.0) is probably 
> technically valid, it most certainly indicates a packaging error (most 
> likely but not necessarily a downstream packaging error).
>
> Should we prevent this error from happening by explicitly erroring (and 
> failing the build) when it happens? I think it would make the dependency 
> generators more robust.
>
> In an unlikely scenario when packagers actually want to package version 
> 0, they can reach out and we can allow it via some configuration (but 
> [YAGNI], so I don't want to clutter the generator with yet another 
> option right away).
>
> [YAGNI] https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it

Sounds like a great idea.

[Charalampos Stratakis]

On Sat, Jan 29, 2022 at 10:12 PM Miro Hrončok  wrote:
> Hello Pythonistas,
>
> today, I've looked up packages in rawhide providing python3dist(...) = 0
> and I
> opened bugzillas for them:
>
> https://bugzilla.redhat.com/showdependencytree.cgi?id=python3dist0
>
> While version 0 (or equal versions like 0.0 or 0.0.0) is probably
> technically
> valid, it most certainly indicates a packaging error (most likely but not
> necessarily a downstream packaging error).
>
> Should we prevent this error from happening by explicitly erroring (and
> failing
> the build) when it happens? I think it would make the dependency
> generators
> more robust.
>
> In an unlikely scenario when packagers actually want to package version 0,
> they
> can reach out and we can allow it via some configuration (but [YAGNI], so
> I
> don't want to clutter the generator with yet another option right away).
>
> [YAGNI] https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it
>
> --
> Miro Hrončok
> --
> Phone: [phone]
> IRC: mhroncok
> _______________________________________________
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]...
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

Makes a lot of sense to error out the build in this case.

[José Abílio Matos]

On Monday, 7 February 2022 13.58.24 WET Charalampos Stratakis wrote:
> Makes a lot of sense to error out the build in this case.

I agree. I can not imagine a case where this makes sense, or if I ever found 
an example where that was ever the case...