pylons/pyramid_exclog

Exception logging tween for Pyramid

Pylons

Pylons is a rapid web application development framework.

Note

Pylons has merged with repoze.bfg, and is now in maintenance-only mode. It's highly recommended that new projects start with the new merged web framework, pyramid.

Install

Read the online Installation instructions.

If you want to install from source you can run the following command:

$ python setup.py install

This will display a message and download setuptools if the module is not already installed. It will then install Pylons and all its dependencies. You may need root privileges to install setuptools.

Testing

To test the source distribution run the following command:

$ python setup.py test

This will install additional dependencies needed for the tests. As above, you may need root privileges.

Documentation

Read the complete Pylons web framework documentation.

Definitive Guide to Pylons is a book about Pylons published by Apress, written by James Gardner, with free HTML rendering.

Generating documentation requires Sphinx:

$ easy_install Sphinx

Then to build the documentation use the commands:

$ cd pylons/docs/<lang>
$ make html

pyramid_exclog's Issues

new release?

version 1.0 throws AttributeError: 'Request' object has no attribute 'registry'

New PyPI release?

I was wondering if it'd be possible to get a new version released to PyPI sometime soon. I'm especially itching to use the new get_message functionality in production.

$(params)s instead of %(params)s

params values are not replaced in global message if an exception occurred

exclog.extra_info allow to get more info about occurred exception but params is not replaced
inside the string because of a bad string format

$(params)s instead of %(params)s

line 62 of init.py main file

Missing license file in a wheel package on PyPI

Hi, the license file is present in a tarball, but missing in a wheel package on PyPI. Please include it.

position tween over pyramid_tm

It seems to me that with pyramid_tm moving over the exception views it may be necessary to move this tween over as well. Minimal changes are required aside from checking request.exception on top of uncaught exceptions. It might be smart as well to add an over=['pyramid_tm.tm_tween_factory', EXCVIEW] constraint.

as_globals_list enforcing a list of strings

Hi,

I noticed that the function as_globals_list in init.py file is using the maybe_resolve method from the resolver, this allows to pass a string that needs to be imported or directly a class which will be untouched.

def as_globals_list(value):
    ...
    value = aslist(value)
    for dottedname in value:
        ...
        resolver.maybe_resolve(dottedname)

However, the method used before the for loop aslist() assumed that everything is a string. Could we follow the same logic that maybe_resolve and handle the case where the value is a class directly?

readme.rst points to https://

readme.rst points to https://

Trouble with Amazon aws : SMTPAuthenticationError: (530, 'Must issue a STARTTLS command first')

I successfully used my aws credentials to send an email.
But when I use it in exclog to send a mail it returns an error:
SMTPAuthenticationError: (530, 'Must issue a STARTTLS command first').

This is the code-

[handler_exc_handler]
class = handlers.SMTPHandler
args = (('email-smtp.us-east-1.amazonaws.com', 587), '[email protected]', '[email protected]'], 'Apnistreet Exception', ('username','user key'))
level = ERROR
formatter = exc_formatter

Could you perhaps look into it and say whether its exclog's problem or mine?

exclog.extra_info missing in pypi (please update pypi)

pypi version is not update to latest version 0.5
documentation talk about exclog.extra_info which is unused
in pypi version

Exceptions while logging are swallowed

Exceptions can be swallowed if:

• pyramid_exclog errors while logging an exception
• pyramid is configured to handle all errors (i.e. to provide a custom internal server error page)

I think the solution is to log any exceptions that are generated while logging.

An example of an exception while logging: #12

testing a fix over here: https://github.com/jinty/pyramid_exclog/tree/failsafe

Custom log handler

Pyramid's narrative documentation is a little short on general exception handling:

To log (or email) exceptions generated by your Pyramid application, use the pyramid_exclog package.

I wonder what I must do to have pyramid_exclog use my custom handler? I'm sending my warnings to airbrake and am using airbrake-python for that.

While your code is pretty short I'm still unsure what exactly I have to patch to get my stuff working. Could you give me a general idea how I should proceed?