And thanks for all your efforts - I also worked with Ofek on
https://peps.python.org/pep-0752/. - which we would love to have for the
Apache Software Foundation (to better follow the rules of the ASF regarding
package naming and typosquatting confusion preventions) - I hope it will be
**finally** accepted soon and it will make it easier for me personally to
take part in workspace PEP when we get there. I would love it if you could
join that effort when the time comes.

On Sat, Nov 8, 2025 at 6:20 PM Jarek Potiuk <[email protected]> wrote:

> Fantastic! Thanks Cary !!! That's great to know !
>
> On Sat, Nov 8, 2025 at 5:33 PM cary hawkins <[email protected]>
> wrote:
>
>> Hi Jarek,
>> I co-authored this with Ofek and I tried to make it work as close to the
>> uv implementation as made sense for how hatch approaches environments
>> compared to uv. Always happy to receive feedback on how it can be improved!
>> I work at AWS and we needed this feature for our internal Python community.
>>
>> I am stepping into a co-maintainer role with Ofek to help continue to
>> make hatch better. And am making more time to get back to some
>> contributions to Airflow again(I have contributed a few things to the AWS
>> provider and the initial OpenSearch provider PR)so you will all likely see
>> me around again more.
>> Cary Hawkins
>>
>> Sent from my iPhone
>>
>> > On Nov 8, 2025, at 4:09 AM, Jarek Potiuk <[email protected]> wrote:
>> >
>> > Hello here,
>> >
>> > I just wanted to let everyone know (as I am watching it closely) - that
>> > there is a workspace support - similar to the uv one -  just merged in
>> > hatch: https://github.com/pypa/hatch/pull/2073 . Hatch is a PyPa
>> (Python
>> > Packaging Authority) project and it's a welcome addition to see that
>> Ofek
>> > and some contributors there are also recognising the needs of supporting
>> > such a feature.
>> >
>> > I am not sure how "close" it is to what "uv" offers, but I think it's a
>> > nice step into starting discussing about some standardisation efforts in
>> > this area and maybe eventually (providing some PEPs will be discussed
>> and
>> > agreed) - turning our "uv workspace" into "PEP-standard workspace"
>> > eventually.
>> >
>> > I will keep an eye on that and maybe even try to get more awareness
>> about
>> > monorepo/workspace needs in the ecosystem. Later on it might maybe turn
>> > into PEP discussions and proposals, so ... stay tuned and if anyone
>> would
>> > like to participate in it, you are most welcome - I will try to keep us
>> > updated here with the progress.
>> >
>> > J.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

Reply via email to