Log file Viewer

[00:04:11] <FunkyBob> morning! am trying to use namespace packages, and it's not behaving how I expected

[00:04:42] <FunkyBob> in my setup.cfg I use find_namespace ... and things install ... but when I install another package contributing to that namespace, it copies into the same directory

[00:05:08] <FunkyBob> my understanding fro mthe pep and how __path__ works, they should exist in separate directories, and be searched by the import machinery

[00:06:24] <FunkyBob> i also saw in the docs for setuptools the need for the __init_- with the call to .declare_namespace()

[00:08:15] <toad_polo> FunkyBob: I don't think the declare namespace thing is right.

[00:12:27] <FunkyBob> no, looks like it's not

[00:12:36] <FunkyBob> am wondering if all the machinery _only- supports top-level namespaces

[00:13:57] <FunkyBob> confirming what you said, toad_polo, from pep420: As a consequence, pkgutil.extend_path and pkg_resources.declare_namespace become obsolete for purposes of namespace package creation.

[00:22:06] <FunkyBob> ok, further reading of teh pep shows indeed it's an option for the packager to install them in the same dir

[00:50:52] <graingert> tos9: no the regex forbids names starting with _.-

[00:51:03] <graingert> tos9 they are only allowed inside the name

[00:51:09] <tos9> graingert: ah, got it

[00:51:09] <graingert> like_.-this

[00:51:27] <tos9> graingert: (but yeah what's wrong with @token, wasn't that the current one?)

[00:51:34] <graingert> windows

[00:51:43] <graingert> or something

[00:51:55] <graingert> `token@pypi.org`

[00:52:05] <graingert> might work

[00:52:22] <graingert> imho __token__ works nice feels kinda python

[01:53:21] <pradyunsg> @graingert: I'm in. 🙃

[01:53:58] <graingert> Noice

[01:55:38] <graingert> There's something nice about tokentokentokentokentokentokentokentokentokentokentoken too