Calling 'import pylon.config' (which is not an actual module) was breaking the build process...
Removed 'import pylons.config', since it was unnecessary and broke th…
…e 'make pyx' process (since pylons.config isn't an actual module...)
pylons.config is definitely an actual importable python object and is used in several places in this file. It sounds like something else is amiss with your build environment. If you'd like help figuring it out, please send a description of the error to our mailing list or dev IRC channel.
According to the documentation for Pylons, pylons.config is a global object contained within the pylons module--in which case, the proper way to import it is with from pylons import config. But even that's not necessary since pylons is already imported in that file, and can be referenced by using pylons.config (which it already is).
from pylons import config
Gotcha. You are correct that the import can be pruned. Reopening.
Merged, thank you! :)