Closed jdicioccio closed 2 weeks ago
Yes. Me too for hatch test
, hatch run types:check
, and hatch build
as well.
+1
+1
Same here!
If it helps, as a workaround I fixed the version to the previous hatchling pip install hatch==1.13.0 hatchling==1.25.0
and everything back to normal.
Same with airflow. Pinning to hatchling 1.25.0 fixes the issue
Unfortunately in my case I don't control the dependency on hatchlings so I can't pin it directly. Is there something akin to a global constraints file for pip?
Ideally, 1.26.0 would be yanked or a patch for hatch released asap.
The hatch-v1.13.0 tag still contains the following code:
https://github.com/pypa/hatch/pull/1582 / adba0033f7a85185c6bca0923ac62e9c73e9796e removed the above code and predates 28bfe354ff23e387a40126b0ead18e3f0e9e3751. Yet, it didn't make it into hatch-v1.13.0. What happened?
The hatch-v1.13.x branch was forked from the master branch too early as far as I can see, and misses most recent changes that are necessary to hatchling 1.26.0, including #1582 / adba0033f7a85185c6bca0923ac62e9c73e9796e.
I think the hatch-v1.13.0 tag should have been applied to the master branch on 28bfe354ff23e387a40126b0ead18e3f0e9e3751, instead it has been applied to the spurious hatch-v1.13.x branch on 4e3c515bb15fd5533ced963c70308e2a271905d9.
The solution is indeed to:
Sorry about that everybody!
1582 / adba003 removed the above code and predates 28bfe35. Yet, it didn't make it into hatch-v1.13.0. What happened?
I have a branch for that minor release because there was a bunch of stuff on master that was not yet ready to be released and it was important to ship support for Python 3.13.
Thanks for a quick fix @ofek . How about yanking 1.26.0 ? I think it's generally broken, so might be good to yank it
It's broken in relation to Hatch only, no?
Yes. That's what we saw - it broke whe we installed hatch, but our packages seemeed to be build correctly. So yes - there is no "strong" need to yank it, but I guess it's no harm either.
True, yanked! https://pypi.org/project/hatchling/1.26.0/
With the just-released 1.26.0, I'm getting the following error when using 'hatch run'