Log file Viewer

[11:30:25] <dstufft> nlh: Why are we changing Projects to Packages

[11:30:33] <nlh> hey

[11:30:33] <nlh> sorry

[11:30:37] <nlh> I was just replying

[11:30:45] <nlh> The problem wasn't more one over the other

[11:30:50] <nlh> just that the current UI was inconsistent

[11:31:02] <nlh> sometimes calling them "packages" sometimes "projects"

[11:31:12] <nlh> I am happy to go with projects, but we'll need to make some changes

[11:31:35] <dstufft> Ok

[11:31:36] <nlh> for example, the main heading should say "Find, install and publish Python projects with the Python Package Index"

[11:32:21] <nlh> I made the assumption that I had introduced the "projects" wording... and it was wrong

[11:32:23] <nlh> sorry :(

[11:32:29] <dstufft> It's not a problem

[11:32:35] <dstufft> that's what git revert is for!

[11:32:38] <nlh> lol

[11:32:39] <nlh> yes

[11:33:00] <nlh> but the main problem is that PyPI is the Python *package* index...

[11:33:09] <nlh> so that's already an inconsistency

[11:33:28] <dstufft> FWIW, I generally try to use PEP 426 definitions for stuff on PyPI -> https://www.python.org/dev/peps/pep-0426/#supporting-definitions except where I hate it (which is a real useful guide line D: )

[11:33:59] <dstufft> mostly that means s/distributions/files/ and /index servers/repositories/

[11:33:59] <nlh> bookmarked :)

[11:34:34] <nlh> the problem is that PyPUG uses "packages" extensively

[11:34:55] <nlh> so there is going to be a disconnect between PyPI and PyPUG

[11:35:21] <nlh> which is a problem because I'm trying to link more to PyPUG to provide better help points

[11:35:22] <dstufft> I hate the name "PyPI" because of the "Package" in it, because of the "Index" in it (PyPI hasn't been primarily an index in YEARS) and because of the fact it rhymes with PyPy

[11:35:36] <nlh> lol

[11:35:56] <nlh> yes, I had that feeling already :P

[11:36:10] <dstufft> basically the only part of PyPI I like is the "Py"

[11:36:12] <dstufft> :D

[11:36:28] <dstufft> for extra fun, https://packaging.python.org/en/latest/glossary/#term-project

[11:36:31] <nlh> lets rename it "PyPlace"

[11:36:39] <nlh> "the place to find python projects"

[11:36:40] <nlh> lol

[11:37:21] <nlh> oh lordy, I've walked into a minefield here

[11:37:47] <nlh> well, from my perspective, the PR that was just merged it better because it is consistent.

[11:38:15] <nlh> (at least internally with the other content on warehouse)

[11:38:58] <nlh> If we change it to projects, I'll need to update https://pypi.io/help/

[11:41:30] <dstufft> (The PR does of course make it inconsistent with the URLs, which are /project/<foo>/)

[11:41:37] <nlh> ah, crap

[11:41:47] <nlh> I don't know

[11:42:17] <dstufft> My suggestion would be to back out the PR, at least for now, and try to get some agreement with packaging.p.o what we're going to call things.

[11:42:38] <nlh> ok

[11:42:42] <nlh> sounds reasonable to me

[11:42:46] <nlh> either way, we're going to have to make changes

[11:42:54] <dstufft> Or, well I guess we don't need to do the backing out really until we have a decision

[11:43:01] <dstufft> it's not going to hurt anything, it's just some text

[11:43:05] <nlh> :P

[11:43:15] <nlh> also, I don't want to dissuade our new contributor straight away :P

[11:43:30] <dstufft> if it had touched the URL structure I would have cared more about backing it out

[11:44:02] <nlh> I would not have merged it if it touched any Python code

[11:44:42] <dstufft> (I'm a bit frustrated these last 2 days because of a CPython discussion, so sorry if I'm a bit short)

[11:44:48] <nlh> no, not at all

[11:45:14] <nlh> so do we open an issue on Warehouse, or do we need to raise this issue somewhere else?

[11:47:17] <dstufft> I would open an issue on Warehouse so we don't forget about it, then either a discussion on distutils-sig or an issue on pypug

[13:59:31] <dstufft> nlh: Ok, I investigated this a bit further-- https://github.com/pypa/warehouse/issues/1252

[13:59:55] <nlh> dstufft: thanks! I'll have a read after work :)

[15:36:24] <robhudson> does setuptools.setup allow a list for the `keywords` arg? Or is it assumed a string? Hard to find docs on it.

[15:41:28] <dstufft> robhudson: If it accepts a list, it's going to coerce it into a string

[22:45:34] <robhudson> dstufft: are there milestones? If I wanted to contribute on a regular basis is there something I can track that shows me important things?

[23:01:08] <dstufft> robhudson: https://github.com/pypa/warehouse/issues?milestone=1 is the most important one right now

[23:03:28] <robhudson> thanks