* Revert "Remaster midnight theme for hierarchical styles"

This reverts commit c7a8fbb0.

* Clean up some of the colors in the midnight theme

- Add some colors for some extra Python tokens
- Make the current line easier to see
- Add back the link() calls from the reverted c7a8fbb0 (although I'm unsure
  what they do)

* Make the command line not bold in the midnight theme

* Use the default text color in the midnight theme

The theme claims to be best with green text, so we also use white instead of
green for the comment color.

* More cleanups to the midnight theme

- Make the highlighted line always blue instead of green
- Fix some color combinations that were hard to read
- Be consistent about highlighted and active things in the sidebar. Active is
  bold, highlighted is blue background, disabled is gray. In the variables
  view green (and lighter green for highlighted) is used for highlighted
  variables.
- Use lighter and darker yellow (actually brown and yellow) for the current
  line highlighted and not highlighted.
- Make the sidebars lighter when selected
- Make the hotkeys italics as well as underlined, since the underline is very
  hard to see

Some issues:

- The bold dark gray for disabled highlighted breakpoints is just showing as
  bold white. Don't know if that's a bug in my terminal or a bug in urwid, or
  if they really do just look the same.
- The hotkey letter in the highlighted pane does not change. Should there be a
  "focused hotkey" color?

* Fix flake8 issues

* Make some changes to the midnight theme from the review by @mvanderkamp

* Use light green as the main color for midnight instead of dark green

* Color operators in dark green in the midnight theme

* Some tweaks to the midnight theme based on review

* Get rid of some redundant settings in the midnight theme

* Implement "--continue" CLI arg (alias "-c")

* Rename _continue -> _continue_at_start

    - Use _continue_at_start__setting for attribute to differentiate
      from the existing _continue_at_start attribute

* Extract _waiting_for_mainpyfile()

* Add help text

* Fix zsh completion of `--pre-run`

Refer https://github.com/zsh-users/zsh/blob/master/Completion/Unix/Command/_sudo#L47-L51
the original completion of `--pre-run` will complete external commands, environment variables, built-in functions of zsh, etc.
Now it only complete external commands, which is expected result of `--pre-run`: it cannot run built-in functions of shell.

* Change pudb3 to pudb

Wu Zhenyu authored Aug 13, 2022 and Andreas Klöckner committed Aug 20, 2022

Modified from <https://github.com/ytdl-org/youtube-dl/tree/master/devscripts>

1. `scripts/zsh_completion.py`
2. `sudo mv _* /usr/share/zsh/site-functions`
3. `compinit`

Lumir Balhar authored Jul 29, 2022 and Andreas Klöckner committed Jul 31, 2022

See changes in CPython
https://github.com/python/cpython/pull/94562
https://peps.python.org/pep-0626/

* Fix critical bug when re-entering IPython 8.4.0+ external shell

- IPython 8.4.0+ performs at-exit operations after calling mainloop
  (introduced by 08d54c0e367b535fd88aca5273fd09e5e70d08f8 commmit),
  breaking necessary PuDB functionality. This prevents re-entering
  IPython shell
- Quick fix sets/unsets internal shell._atexit_once_called property
  during run_ipython_shell_v11, preventing those operations from being
  executed

* Fix "E501 line too long" error from flake8

- Bug start in IPython 8.0.0. Update comment accordingly.

Co-authored-by: Vladyslav Sydorov <vlad@vsydorov.com>

* Replace fcntl/termios with os.get_termianl_size()

* Replace fcntl/termios with os.get_terminal_size()

* Removed unused import (struct)

* Removed unused import (struct)

if/mkdirs may race during parallel test runs.

Raul Benencia authored Jul 19, 2022 and Andreas Klöckner committed Jul 19, 2022

This contribution replaces code marked as LGPL to avoid conflicts with
the MIT license used in this project. Moreover, it simplifies the code
by removing the *resource parameter in the get_save_config_path
function, given that it isn't used in this project. It also removes
the xdg_data_home global variable, as it isn't in use either.

For context, in Debian we need to resolve this violation to keep the
package in the archive:

  https://bugs.debian.org/1005854

Tim Gates authored Jul 13, 2022 and Andreas Klöckner committed Jul 14, 2022

There are small typos in:
- doc/starting.rst
- test/test_var_view.py

Fixes:
- Should read `various` rather than `variaous`.
- Should read `utilities` rather than `utitlities`.
- Should read `expected` rather than `extected`.
- Should read `differently` rather than `diffrently`.
- Should read `course` rather than `couse`.

* `pudb.run`: Expose version information

Calling `python -m pudb.run -v` (**exactly!**), or using `--version` flag,
it prints the version information and exits.

Additionally, added tests to safeguard functionality.

Fixes https://github.com/inducer/pudb/discussions/527



Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>

* flake8 E501

Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>

Co-authored-by: Stavros Ntentos <11300730-stavros-relex@users.noreply.gitlab.com>

Do not treat empty input in line number dialog as zero (avoids spuriously jumping to beginning of file)

In post-mortem mode, the same frame object may occur multiple times.

Michael van der Kamp authored May 20, 2022 and Andreas Klöckner committed May 20, 2022

Simple way of addressing #516 and similar issues that could crop up from bugs / incomplete implementations in container methods.

* added configurable key bindings

* added configurable key bindings

* Update README.rst

* Added flake8 fixes

* Move key config docs to docs

Co-authored-by: Cibin Mathew <cibinmathew@users.noreply.github.com>
Co-authored-by: Andreas Kloeckner <inform@tiker.net>

Blair Bonnett authored Feb 05, 2022 and Andreas Klöckner committed Feb 05, 2022

This is already in requirements-dev.txt but should be here as well as some of the unit tests fail to run without its `mocker` fixture.