#pyramid

[redacted]

[redacted]

[redacted]

[redacted]

[redacted]

[redacted]

dowwie: there is a class called Resolver

don't know where one imported it

dowwie: importable paths can be done via importlib or you can copy pyramid's DottedNameResolver for an old-school / slightly more robust approach

importlib will let you import modules, but you still need to get the class/func yourself whereas the resolver will do it all

[redacted]

dowwie: fwiw here's some code I ripped out of pyramid to use in a separate project https://gist.github.com/mmerickel/a5920b7594158...

[redacted]

long story short, using __import__ is not something that "just works"

[redacted]

[redacted]

[redacted]

there is not a standard format for referencing objects inside a module either... python only dictates the path to the module (foo.bar)

if you want a class/func in that module then historically there are two formats... foo.bar.Baz or foo.bar:Baz

pyramid supports both... the code I ripped out only supports the former... pkg_resources and setuptools typically use the latter

[redacted]

[redacted]

[redacted]

the colon approach is used in setup.py metadata frequently for entry points

[redacted]

[redacted]

basestring is a python2 parent for unicode and bytes

[redacted]

[redacted]

[redacted]

dstufft: https://pypi.org/ nice!

r0sk: :]

er

raydeo: ^

edging closer!