On Thu, May 15, 2025 at 11:27:29PM +0100, Stuart Henderson wrote:
> On 2025/05/15 22:16, Mikolaj Kucharski wrote:
> > I am not sure do I see this right, but with py-aiomqtt 2.4.0 all
> > previously attached dependencies can be dropped and switch to
> > hatchling is enough?
>
> yes, they switched.
On 2025/05/15 22:16, Mikolaj Kucharski wrote:
> I am not sure do I see this right, but with py-aiomqtt 2.4.0 all
> previously attached dependencies can be dropped and switch to
> hatchling is enough?
yes, they switched. that's simpler, let's ignore poetry-dynamic-versioning
for now then.
> See at
I am not sure do I see this right, but with py-aiomqtt 2.4.0 all
previously attached dependencies can be dropped and switch to
hatchling is enough?
See attached tarball.
--
Regards,
Mikolaj
aiomqtt,v3.tgz
Description: application/tar-gz
Here is refresh and patch against -current
I did update:
- devel/py-dunamai
- devel/py-poetry-dynamic-versioning
I did not update:
- net/py-aiomqtt
as version 2.4.0 failed with:
===> Building for py3-aiomqtt-2.4.0
* Getting build dependencies for wheel...
Traceback (most recent call last):
Could this go in Stuart?
I see that depds which you proposed here are in newer version upstream,
but I could look into updating them after what you attached here goes
in.
I am using py3-aiomqtt-2.3.0 from that time when you posted it and it
works here.
On Tue, Mar 25, 2025 at 09:48:40AM +, S
On 2025/03/25 06:15, Mikolaj Kucharski wrote:
> * Getting build dependencies for wheel...
>
> Traceback (most recent call last):
> File "/usr/local/lib/python3.12/site-packages/pyproject_hooks/_impl.py",
> line 402, in _call_hook
> raise BackendUnavailable(
> pyproject_hooks._impl.BackendUn
I am not sure is this good idea, but I manage to make the port with:
Index: pyproject.toml
--- pyproject.toml.orig
+++ pyproject.toml
@@ -57,8 +57,8 @@ strict = true
metadata = false
[build-system]
-requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning>=1.0.0"]
-build-backend = "poetry_
