#pycon-us-2023
1 messages · Page 1 of 1 (latest)
hi! I'm here until Tuesday of the sprints
i'm here until wednesday
Just landed
will be here until Tuesday
here til the end of the sprints!
I’m here until the end of the sprints, but plan to spend a day hiking if possible
let's use this channel for the summit. no, ofek isn't here
thanks @dire fjord
I wonder how the association proposal interacts with the council proposal: https://discuss.python.org/t/proposal-to-create-a-python-packaging-council/25469
As the recent Packaging strategy discussions have revealed, there is an appetite for a council or authority that would set a vision, settle technical disputes, and act as an authority on decisions for the packaging community (or at least for the PyPA). This council would define the vision for the Packaging community and projects, and work in tan...
I know naming is a nuisance, but end users might be glad to understand that pypa works as a group of various projects, and not as this single authority
It’s honestly surprising this thread was never mentioned by anyone
Same! All the organisers were surprised about that too!
no, but I want to one day!
maybe time for the second part of the summit?
or somewhere in between
I did hear from the various topics that we have a need to improve the docs and possibly call for a group that is better set up to coordinate the effort
Somewhere in between, and around. We don't have all the stakeholders here anyway.
yeah, indeed
Yup! One of my motivations for https://pradyunsg.me/lutra/ is that I want to have a rich site structure with good navigation options.
loving this @modern vessel
And the packaging documentation improvements are pipelined after this; which is a separate pipeline from the lock file story and the governance/political restructuring. 🙃
And, it needs me to decide what to do about these things.
themes are of course a controversial topic lol but can we not just use Material for MkDocs? https://squidfunk.github.io/mkdocs-material/
I'd be surprised if it didn't offer everything we want, and also it's nice to outsource something that is not our core competence to a project that is well-funded
Because intersphinx IIRC.
But let's avoid the documentation tooling discussion here.
so many pitfall topics 😄
miketheman
will the slides of the packaging summit be posted online? i wanted to share some of the slides around the very different user groups
There's an open space scheduled on security for package maintainers today: https://twitter.com/di_codes/status/1649818045685325825
I am not in pycon but trying to read here/mastodon to sync up.
I've added mine to the summit notes
thank you!
Added mine as well
Just got to the venue. Anyone around?
Since I couldn’t find the link anywhere—Notes from the Packaging Summit during PyCon US 2023
https://hackmd.io/mjzP1yvOTTSY8TdufaKYzg
Wait, we weren't sharing that just yet coz it needed polishing and needs to be marked as read-only!

Too late 🙂
Pip should be considered more of an API spec that could be overrable rather than a particular implementation
This suggestion sounds interesting
I'm not sure I understand what that means, hopefully polishing helps with that 😛
In the particular context, from what I understand, essentially treat pip to package installation as CPython to the Python language
I’m in the hallway in case anyone needs me (probably no-one but just in case…)
Much nicer to sit out here than in the room.
isn't that already the case?