David Bremner writes:
> To expand on my previous (terse) remarks, when python3 support lands
> upstream, I'll have a look at packaging it. When I say upstream
> already knows, it's because you pointed me to a posting on upstream's
> mailing list. But in case that got lost I also filed an upstream
Brian May writes:
> David Bremner writes:
>
>> IMHO the right place to deal with this is upstream. And presumably upstream
>> already knows?
>
> I am not sure of the best contact for upstream. Presumable the package
> maintainer has good contacts with upstream (Matt Palmer is listed as the
> pac
David Bremner writes:
> IMHO the right place to deal with this is upstream. And presumably upstream
> already knows?
I am not sure of the best contact for upstream. Presumable the package
maintainer has good contacts with upstream (Matt Palmer is listed as the
package maintainer?). Talking to up
Brian May writes:
> Source: ledger
> Version: 3.1.2~pre1+g3a00e1c+dfsg1-2+b1
> Severity: wishlist
>
> Apparently there is a fork with Python 3 support here:
>
> https://github.com/afh/ledger/tree/wip/python3
>
> This is referenced here:
>
> https://groups.google.com/forum/#!topic/ledger-cli/C99w-
Source: ledger
Version: 3.1.2~pre1+g3a00e1c+dfsg1-2+b1
Severity: wishlist
Apparently there is a fork with Python 3 support here:
https://github.com/afh/ledger/tree/wip/python3
This is referenced here:
https://groups.google.com/forum/#!topic/ledger-cli/C99w-79Jq8o
I am not sure what the current
5 matches
Mail list logo