While dealing with multiple exceptions ("During handling of the above exception, another exception occurred: ..."), Pretty Errors will show only the last one.

Is there a way to show all of them?

The site-packages/sitecustomize.py file is not reliable loaded for everybody. To ensure pretty_errors is loaded after python -m pretty_errors, create a site-packages/pretty_errors.pth file containing:

import pretty_errors; pretty_errors.configure() # if you add option here, keep it on one line

If you don't want to use a *.pth, at least use /home/user/.local/lib/python3.7/site-packages/usercustomize.py, which is more likely to be imported and is meant for things like this. But *customize.py files are not imported in venv, which makes them pretty useless for real life Python usage.

Attempting the global install via python -m pretty_errors under a virtual environment with path C:\venvs\flask results in this trace:

runpy.py 193 _run_module_as_main "main", mod_spec)

runpy.py 85 _run_code exec(code, run_globals)

main.py 133 found = find_install(True)

main.py 66 find_install for path in getallsitepackages():

main.py 54 getallsitepackages return getsitepackages() + getusersitepackages()

main.py 42 getsitepackages pattern = re.compile(r'^%s$' % os.path.join(os.environ['VIRTUAL_ENV'], 'lib', 'python[0-9.]+', 'site-packages'))re.py 233 compile return _compile(pattern, flags)

re.py 301 _compile p = sre_compile.compile(pattern, flags)

sre_compile.py 562 compile p = sre_parse.parse(p, flags)

sre_parse.py 855 parse p = _parse_sub(source, pattern, flags & SRE_FLAG_VERBOSE, 0)

sre_parse.py 416 _parse_sub not nested and not items))

sre_parse.py 502 _parse code = _escape(source, this, state)

sre_parse.py 401 _escape raise source.error("bad escape %s" % escape, len(escape))

sre_constants.error: bad escape \l at position 15

I attempted to fix by using the method described in another issue, changing regex pattern to allow backslashes in path. But then there is no option to install anywhere:

(flask) C:\Users\dkornacki\rtc-workspace\iSeries Python\iSeries Python\square_po_import>python -m pretty_errors

To have pretty_errors be used when you run any python file you may add it to your usercustomize.py (user level) or sitecustomize.py (system level), or to pretty_errors.pth.

(just hit to accept the defaults if you are unsure)

Choose folder to install into:

0: Exit

Option: [default: 0]

Hello there, I'd like to use pretty errors in my web development, but I have some issues.

I use the fastapi framework, which runs multi processes through the ASGI uvicorn server. Doesn't matter what I do (import, setup config, usercustomize.py etc.) errors do not get pretty in this context. They do when I run my normal scripts.

Can I ask for help/directions?

Hi~, When I installed pretty_errors via pip, I inadvertently chose let it act on all my envs. Therefore, how can I fully uninstall it or do something to fix it? Thank u~

Or do I have to add pretty_errors.configure( separator_character = '*', filename_display = pretty_errors.FILENAME_EXTENDED, line_number_first = True, display_link = True, lines_before = 5, lines_after = 2, line_color = pretty_errors.RED + '> ' + pretty_errors.default_config.line_color, code_color = ' ' + pretty_errors.default_config.line_color, truncate_code = True, display_locals = True ) at the beginning of each file.

I'm on Ubuntu 20.04 and attempting to install pretty_errors using the python -m pretty_errors -s -p command within a virtualenv. Upon running the command, I get the following output:

To have pretty_errors be used when you run any python file you may add it to your usercustomize.py (user level) 
or sitecustomize.py (system level), or to pretty_errors.pth.

(just hit <enter> to accept the defaults if you are unsure)


 Choose folder to install into:

0: Exit

Option: [default: 0]

After which I hit enter and the install fails. Investigating the __main__.py file along with Issue #38 lead me to the following function on line 41

def getsitepackages():
    pattern1 = re.compile(r'^%s$' % re.escape(os.path.join(os.environ['VIRTUAL_ENV'], 'lib', 'python[0-9.]+', 'site-packages')))
    pattern2 = re.compile(r'^%s$' % re.escape(os.path.join(os.environ['VIRTUAL_ENV'], 'lib', 'site-packages')))
    paths = [path for path in set(sys.path) if pattern1.search(path) or pattern2.search(path)]
    return paths

Using some basic debugging, I discovered that the paths variable returned was completely empty, despite the fact that pattern1 should have match my virtualenv path: /home/username/.virtualenvs/general/lib/python3.9/site-packages I traced the source of this error to the call to re.escape in pattern1. The os.path.join call returns /home/username/.virtualenvs/general/lib/python[0-9.]+/site-packages as expected, but the call to re.escape returns the string '/home/username/\\.virtualenvs/general/lib/python\\[0\\-9\\.\\]\\+/site\\-packages'. Because re.escape escapes all regex special characters, the python[0-9]+ portion of the regex gets mangled and causes pattern1.search to fail. Omitting the call to re.escape matches the string as expected. Upon removing the call to re.escape and running python -m pretty_errors -s -p again, everything installed and functioned as expected.

>>> import os, sys, re
>>> sys.path
['', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/home/username/.virtualenvs/general/lib/python3.9/site-packages']
>>> venv_path = sys.path[-1]
>>> os.path.join(os.environ['VIRTUAL_ENV'], 'lib', 'python[0-9.]+', 'site-packages')
'/home/username/.virtualenvs/general/lib/python[0-9.]+/site-packages'
>>> pattern1_escape = re.compile(r'^%s$' % re.escape(os.path.join(os.environ['VIRTUAL_ENV'], 'lib', 'python[0-9.]+', 'site-packages')))
>>> pattern1_escape.search(venv_path)
>>> pattern1_no_escape = re.compile(r'^%s$' % os.path.join(os.environ['VIRTUAL_ENV'], 'lib', 'python[0-9.]+', 'site-packages'))
>>> pattern1_no_escape.search(venv_path)
<re.Match object; span=(0, 61), match='/home/username/.virtualenvs/general/lib/python3.9/s>
>>> pattern1_no_escape.search(venv_path).group(0)
'/home/username/.virtualenvs/general/lib/python3.9/site-packages'

Here is my pyvenv.cfg file for Python and virtualenv info:

home = /usr
implementation = CPython
version_info = 3.9.5.final.0
virtualenv = 20.4.6
include-system-site-packages = false
base-prefix = /usr
base-exec-prefix = /usr
base-executable = /usr/bin/python3.9

Hello there,

Thanks for creating this awesome lib :). I've been using it for few hours and I just cannot get it to work with pytest.

Example code:

import pretty_errors
pretty_errors.replace_stderr()
def test_abc():
    assert 1==1
    a = ''
    print("ok")
    b = a[0]

Terminal output:

Is there anyway to make it work with pytest? Thanks a lot :).

When trying to change configs globally by uncommenting the pretty_errors.configure( in usercustomize.py, an error is thrown since time is not imported, but is used in timestamp_function = time.perf_counter.

On my end, I've just added import time to the top of the file; however, when generating the file import time should be added as well.

Hi, I ran sudo python -m pretty_errors and tried installing both sitecustomize.py and pretty_errors.pth (not at the same time) but, pretty_errors does not seem to work.

When installing either of the files, I installed them at /usr/local/lib/python3.8/dist-packages.

With "sitecustomize.py" it simply does not have any effect. With "pretty_errors.pth" it shows error

Error processing line 2 of /usr/local/lib/python3.8/dist-packages/pretty_errors.pth:

  Traceback (most recent call last):
    File "/usr/lib/python3.8/site.py", line 175, in addpackage
      exec(line)
    File "<string>", line 1, in <module>
    File "/usr/local/lib/python3.8/dist-packages/pretty_errors/__init__.py", line 1, in <module>
      import sys, re, colorama, os, time, linecache
  ModuleNotFoundError: No module named 'colorama'

Even though, Colorama is installed and I the latest version. How do I solve this issue?

support virtualenv

1. fix bug: in virtualenv, run python -m pretty_errors [option] throws
   AttributeError:
   module 'site' has no attribute 'getsitepackages'
2. when run python -m pretty_errors, support displaying sitecustomize.py
   or pretty_errors.pth according to the path you selected before.

This issue is the same as #39, unclear why it resurfaced.

When pretty_errors is run as a module inside a pyenv virtualenv to add it to Python startup procedure (python -m pretty_errors), no folders to install into are found.

Updating the regexes should resolve this.

As a workaround I hardcoded the path to site-packages:

vim $(pyenv prefix)/lib/python3.9/site-packages/pretty_errors/__main__.py

# set paths in line 50 to
            # paths = ['<$(pyenv prefix)>/lib/python3.9/site-packages']

After installing PrettyErrors with pip install pretty-errors or with python -m pip install pretty_errors makes all .pyw files unusable. When i unistalled PrettyErrors .pyw files worked again.

It seems like there is a display_locals which will show local variables. This is very useful, but often functions are short and the exception can be easily understood by looking at the arguments passed to the function. Is there a setting to display function arguments as well as local variables?

The stack trace pretty errors outputs is that of the main thread. Say I have a task in a thread pool that raises an AssertionError. pretty errors just outputs "AssertionError".

runpy.py 196 _run_module_as_main
"/Users/me/.asdf/installs/python/3.10.0/lib/python3.10/runpy.py", line 196
return _run_code(code, main_globals, None,



ap_rescheduler.py 179 reschedule_aps
"xxx.py", line 179
new_schedule = future.result()


_base.py 438 result
"/Users/me/.asdf/installs/python/3.10.0/lib/python3.10/concurrent/futures/_base.py", line 438
return self.__get_result()



_base.py 390 __get_result
"/Users/me/.asdf/installs/python/3.10.0/lib/python3.10/concurrent/futures/_base.py", line 390
try:
    raise self._exception
finally:

self: None

AssertionError

Disabling pretty errors temporarily with PYTHON_PRETTY_ERRORS=0 shows a better trace in that it shows me where the assertion failed.

concurrent.futures.process._RemoteTraceback: 
"""
Traceback (most recent call last):
  File "/Users/me/.asdf/installs/python/3.10.0/lib/python3.10/concurrent/futures/process.py", line 243, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "foo.py", line 463, in bar
    assert False
AssertionError

Is there a setting or trick to enable this while using pretty errors? Thank you.

Is it possible to have PrettyErrors handle exception outputs when using Python's pdb?

I've used the following code to import PrettyErrors

import pretty_errors
pretty_errors.replace_stderr() 

but when adding breakpoints within the code the output is not being interpreted. E.g when running python -m pdb -c continue myscript.py