Thanks for pointing this out.
I’ll unretire typer and typer-cli, then, and give it another chance.
It’s been less than eight weeks (only a few days!) so unretirement will
be quick and will not require re-review.
A little communication from the upstream maintainer would have really
helped!
- Ben
On 8/30/21 6:22 AM, Chandan Kumar wrote:
> Hello Ben,
>
> On Sat, Aug 21, 2021 at 12:36 AM Ben Beasley <ben(a)musicinmybrain.net> wrote:
>>
>> Unless someone convinces me of another plan, I intend to retire
>> python-typer and python-typer-cli in F35 and Rawhide in one week
>> (2021-08-27).
>>
>> I myself introduced these two packages to Fedora quite recently
>> (
https://bugzilla.redhat.com/show_bug.cgi?id=1964742,
>>
https://bugzilla.redhat.com/show_bug.cgi?id=1974118). No other packages
>> currently depend on them.
>>
>> Upstream was in a period of inactivity that was not too worrisome at the
>> time, but has become much more concerning as they have not responded at
>> all to issues or PR’s on this project and have not made the necessary
>> (nontrivial) changes to work with the new major release (8.x) of
>> python-click. Please see
https://github.com/tiangolo/typer/issues/313
>> for an overview of the situation and links to additional relevant issues.
>>
>> It might be possible to sustain these two packages in Fedora 35 by
>> introducing a click 7.x compatibility package, but this is not a
>> long-term solution, and I have no confidence that these projects will be
>> sustainably maintained in the future.
>>
>
> typer-0.4.0 got released today.
>
https://github.com/tiangolo/typer/releases/tag/0.4.0
>
> I think it addresses the above issue related to click 7.x compatibility package,
>
> As per
https://github.com/tiangolo/typer/issues/313#issuecomment-908181587
> ```
> I just released Typer 0.4.0, which is compatible with both Click 7 and Click 8.
> ```
> I hope it helps.
>
> Thank you for maintaining it.
>
> Thanks,
>
> Chandan Kumar
>