It seems like the Pythonic way to handle import warnings is using the warnings module.
This pull request addresses issue #83 by raising a RuntimeWarning instead of writing to sys.stderr. This means that an warning is generally still presented to the user on import, but that the importer may choose how those warnings are displayed. With the current implementation, for instance, pyScss will write to stderr during uWSGI's import of a WSGI application that uses pyScss. Not a good thing.
It seems like the Pythonic way to handle import warnings is using the warnings module.
This pull request addresses issue #83 by raising a RuntimeWarning instead of writing to sys.stderr. This means that an warning is generally still presented to the user on import, but that the importer may choose how those warnings are displayed. With the current implementation, for instance, pyScss will write to stderr during uWSGI's import of a WSGI application that uses pyScss. Not a good thing.