/j #bandersnatch
#resources
old summit
can you clarify?
floral lagoon
Was just seeing if I could make a bandersnatch channel
Already more closed than IRC by default
old summit
Done for you
floral lagoon
Sweet - Thanks
cerulean lynx
Would a #manylinux channel be a good idea, @real seal ? I'd like to ask if adding a tracking issue for PEP 656 rollout would be a good idea.
old summit
Sure we can, generally I wait for a maintainer to request it 🙏 just so that we know we have someone representing the project here
cerulean lynx
I suspected as much, which is why I tagged @real seal 😉
dire cobalt
would it make sense to have channels for packaging related projects, even if they are not technically in the pypa, as we have the maintainers here? the specific examples I am interested in is importlib_resources and importlib_metadata
old summit
That's up to those packages maintainer I'd say 😎 if they're happy to maintain that channel sure
dire cobalt
sounds good
harsh nymph
@dire cobalt might make sense to make a new category for them so its easier to separate "pypa owned", and "packaging related"
dire cobalt
sure
fast crest
I wonder if we should just rename this discord to "Python Packaging" at this point.
If we're adding non PyPA projects, it makes sense IMO.
old summit
Dunno, all packaging projects are free to join PyPA and I'd prefer that 😂
fast crest
I mean, I'm pretty sure importlib_resources would just live on it's own for example.
fast crest
I didn't say they can't. :)
We can change the URL btw.
server settings > vanity url (if you're admin)
old summit
To be fair pypa can be also shortcut for python packaging, so nothing needs to change then 🤷♂️
I'm personally voting on the side to keep it as is :-) but maybe other people think differently.
lone beacon
pypa can be also shortcut for python packaging
We can drop the A (not the first time someone says this). Only downside is everyone will suffer pronouncing pip and PyP 😆
old summit
oh definitely not, seems like horrible to say and distinguish from pip
floral lagoon
Would y’all welcome black here? We’re looking for a more open place to chat. Since there is already not “pypa” packages …
old summit
pypa is more in spirit of python packaging 😄 then PyPA, as joining that org is optional for python packaging
dense iron
I mean, cooper, that's a stretch
old summit
that being said selling black as python packaging feels like really pushing it, though personally I'd love to see it xD
dense iron
if not completely unrelated haha
floral lagoon
Selfishly, just means less places for me to hang out 🤣
dense iron
yeah, me too as a black maintainer as well, but let's not muddy the waters for this server :p
old summit
in theory black could have its own Discord server 🙂 though you might want a linter umbrella one instead, aka https://github.com/PyCQA I think would be that
floral lagoon
I have no idea who “runs” that
old summit
me neither xD 😄
floral lagoon
And I maintain flake8-bugbear
old summit
Id' assume someone from https://github.com/orgs/PyCQA/people?type=source
if not all 🙂
So yeah, I'd say no for black for now, and encourage you to setup a pycqa server instead 🙂 and arguable black can well fit under that 🙂
dense iron
I can only agree.
floral lagoon
There are reasons black isn’t there
old summit
There are reasons black isn’t there
from my limited knowledge on the topic those were more political than technical 🙂
floral lagoon
Ya, haters
cerulean lynx
What about a setuptools_scm channel, @harsh nymph ? I wanted to ask about versioneer's ability to get the version from a git tarball; maybe an example for how to do that inside setuptools_scm might be interesting?
harsh nymph
What about a setuptools_scm channel, <@!233155068155658240> ? I wanted to ask ab...
Reminds me that I wanted to get that into setuptools_scm itself
dire cobalt
btw, I can create a channel for you if you want
cerulean lynx
Reminds me that I wanted to get that into setuptools_scm itself
That would be awesome! Though this already looks useful. I assume it would work with pyproject.toml requires.
harsh nymph
That would be awesome! Though this already looks useful. I assume it would work ...
I'll include it in a way that will work similar to the prototype @dire cobalt made for his tool, i want to make it standardised
real seal
Would a #manylinux channel be a good idea, <@!838464137993912331> ? I'd like to ...
Would a #manylinux channel be a good idea, @real seal ? I'd like to ask if adding a tracking issue for PEP 656 rollout would be a good idea.
I'm sure lacking behind on Discord... Will try to get here more often.
A #manylinux channel might be a good one.
For PEP 656 (musllinux), is pypa/manylinux the right fit ? It might be misleading with such a name but that would probably be my only argument against. If there's consensus it should get in there, I'll welcome such a contribution with open arms.
Up til now, I saw that @lone beacon got this into pypa/packaging which is probably the most important to get pip support as early as possible. There's also a lengthy thread (help wanted) at pypa/auditwheel to get support for this https://github.com/pypa/auditwheel/issues/305
lone beacon
Probably better to split by project, I’d prefer having auditwheel (covering all linux tags) than manylinux
Unfortunately I haven’t got too much time to actually write any code for musllinux support
cerulean lynx
Can someone (re)enable pre-commit.ci on cibuildwheel?
Actually, maybe I have permission to do that, or at least request it.
When I try, it goes from "selected two repositories" (and doesn't say which ones) to "selected one repository" with cibuildwheel listed. I think this was the problem @real seal had with Travis, too?
I'll wait for someone else to do it, I think if I try it might remove it from the existing repositories.
real seal
I think this was the problem @real seal had with Travis, too?
most probably
it lets you think you add something without warning it'll remove some things...
pypa org owners shall be able to see everything and thus keep what's already installed when adding something new.
@fast crest or @umbral sparrow ?
real seal
yes, to be added to cibuildwheel please
cerulean lynx
I think if someone changes it, they are only able to select things they control, and for some bizarre reason, GitHub removes the existing integrations that you aren't supposed to have access to! I should not be able to remove pre-commit.ci from the projects I can't add it to, but I think that's what it was going to do, from @real seal's experience and the number of repos count.
fast crest
yes, to be added to cibuildwheel please
Donezo!
harsh nymph
<@&815744082823348274> for "whops" reasons it seems like i'm the admin of the pypa channel on matrix.org (and it seems there is a number of gitter based pypa channels around as well) im wondering what to do about those
old summit
for the virtualenv gitter I've marked it as not in use anymore, and forward people here 🙂
harsh nymph
ok, im going to do that for the pypa gittern channel then
eh matrix i meant
is there a vanity link for pypa?
ah, found it
oh, interesting, when i leave the pypa channel on discord it will be gone
old summit
is there a vanity link for pypa?
harsh nymph
I'm not sure why everyone's congregating on a proprietary platform
Right now I believe primarily ux and some features, i find discord way easier to manage than matrix atm, i hope that gap resolves soon
plain frost
Discord unquestionably has better UX and more features but for people interested in FOSS sacrificing some of that convenience to support an open platform doesn't seem like a terribly bad idea.
earnest rose
discord.gg/pypa
how does this server have a vanity link with so few members?
oblique spade
earnest rose
wow
cerulean lynx
Mergery seems not be activated on cibuildwheel? See https://github.com/pypa/cibuildwheel/pull/713 . Maybe it was activated before the switch over. @undone meteor didn't like adding required branches to get the official auto-merge feature, because it made old PRs show orange dots even though they passed at the time they were merged. (Don't know / think that has been fixed)
