Hi everyone,

Just a small word to say that Offpunk 2.0 will be released next week, 
depending on finding the time to write the related blog post.

I consider current code as 2.0 final. I’ve also already updated the 
changelog.

If you have any bug/issue/typo that should be fixed before releasing 
2.0, please tell me. (only 3 issues left open for now and I don’t plan 
to fix them for 2.0).

Documentation is also lagging. I’m sorry for that. Hope to improve it 
gradually after 2.0.


Thanks for your contribution to this upcoming release.


-- 
Ploum - Lionel Dricot
Blog: https://www.ploum.net
Livres: https://ploum.net/livres.html

Le dimanche 12 novembre 2023 à 14:51 +0000, Ploum a écrit :
> If you have any bug/issue/typo that should be fixed before releasing
> 2.0, please tell me. (only 3 issues left open for now and I don’t plan 
> to fix them for 2.0).


I'd recommend fixing the timg version in pyproject.toml, or
"pip install offpunk[timg]" will give quite confusing errors :)

Best,
Jean

On 23/11/12 10:24, Jean Abou Samra wrote:
>Le dimanche 12 novembre 2023 à 14:51 +0000, Ploum a écrit :
>> If you have any bug/issue/typo that should be fixed before releasing
>> 2.0, please tell me. (only 3 issues left open for now and I don’t plan
>> to fix them for 2.0).
>
>
>I'd recommend fixing the timg version in pyproject.toml, or
>"pip install offpunk[timg]" will give quite confusing errors :)

There’s a problem here because the "timg" pypy project is an old, 
outdated, unmaintained project which is unrelated to the timg python 
expect (which is not a python software but a binary).

Pypy project: https://github.com/adzierzanowski/timg

"real" timg: https://github.com/hzeller/timg

This is an interesting confusion. I don’t know if there’s a "proper" way 
to solve this.

In the meantime, I will simply remove the timg dependency as it is 
anyway deprecated by chafa (which is not part of the pyproject.toml).

Does it make sense to put non-python dependencies in the pyproject.toml? 
I see that "file" is in there. Once again, it is the "file" unix tool 
which is used, not any python binding.

Le dimanche 12 novembre 2023 à 21:51 +0000, Ploum a écrit :
> There’s a problem here because the "timg" pypy project is an old, 
> outdated, unmaintained project which is unrelated to the timg python 
> expect (which is not a python software but a binary).
> 
> Pypy project: https://github.com/adzierzanowski/timg
> 
> "real" timg: https://github.com/hzeller/timg
> 
> This is an interesting confusion. I don’t know if there’s a "proper" way 
> to solve this.
> 
> In the meantime, I will simply remove the timg dependency as it is 
> anyway deprecated by chafa (which is not part of the pyproject.toml).
> 
> Does it make sense to put non-python dependencies in the pyproject.toml? 
> I see that "file" is in there. Once again, it is the "file" unix tool 
> which is used, not any python binding.


Ah. No, it doesn't make sense to put non-Python dependencies in
the project.dependencies and project.optional-dependencies fields,
because that's for use by resolvers which use Python package indices
(the most important by far being PyPI). There is an ongoing
proposal [*] to add a separate key for other dependencies, but
it's under discussion at the time. For now, the only proper way
to declare these is to document them somewhere.

Linux distros normally don't use the pyproject.toml metadata directly,
because packages often have different names in distros than on PyPI,
and are sometimes split into multiple packages in distros or that
sort of thing.

[*] https://discuss.python.org/t/pep-725-specifying-external-dependencies-in-pyproject-toml/31888

On 23/11/12 10:58, Jean Abou Samra wrote:
>Le dimanche 12 novembre 2023 à 21:51 +0000, Ploum a écrit :
>> There’s a problem here because the "timg" pypy project is an old,
>> outdated, unmaintained project which is unrelated to the timg python
>> expect (which is not a python software but a binary).
>>
>> Pypy project: https://github.com/adzierzanowski/timg
>>
>> "real" timg: https://github.com/hzeller/timg
>>
>> This is an interesting confusion. I don’t know if there’s a "proper" way
>> to solve this.
>>
>> In the meantime, I will simply remove the timg dependency as it is
>> anyway deprecated by chafa (which is not part of the pyproject.toml).
>>
>> Does it make sense to put non-python dependencies in the pyproject.toml?
>> I see that "file" is in there. Once again, it is the "file" unix tool
>> which is used, not any python binding.
>
>
>Ah. No, it doesn't make sense to put non-Python dependencies in
>the project.dependencies and project.optional-dependencies fields,
>because that's for use by resolvers which use Python package indices
>(the most important by far being PyPI). There is an ongoing
>proposal [*] to add a separate key for other dependencies, but
>it's under discussion at the time. For now, the only proper way
>to declare these is to document them somewhere.
>
>Linux distros normally don't use the pyproject.toml metadata directly,
>because packages often have different names in distros than on PyPI,
>and are sometimes split into multiple packages in distros or that
>sort of thing.
>
>[*] https://discuss.python.org/t/pep-725-specifying-external-dependencies-in-pyproject-toml/31888


Thanks a lot for that clarification. I’m thus also removing the "file" 
dependency from the pyprojects.toml.

Thanks for noticing. It is very helpful!

-- 
Ploum - Lionel Dricot
Blog: https://www.ploum.net
Livres: https://ploum.net/livres.html