* upgrade prompt-toolit to 3.0
fix: https://github.com/dbcli/pgcli/issues/1148
related:
https://github.com/prompt-toolkit/python-prompt-toolkit/issues/886
in order to make the `behave` test pass, I have to:
- extend timeout for database connection test.
- extend timeout for basic command expect.
- extend timeout for features/steps/crud_table.py:: see data selected.
- disable cpr for features but "run the cli"
* [ci] disable CPR for all behave tests.
* bugfix: remove duplicated prompt expect.
* [ci] delete CPR env setting.
* Revert "[ci] delete CPR env setting."
This reverts commit fe4d5b565e.
* revert the extending timeout back.
* [ci] test when didn't disable CPR.
* Revert "[ci] test when didn't disable CPR."
This reverts commit d379b1e736.
This file is a bash completion script for pgcli.
It allows to <tab> complete database names, users and hosts, plus showing the other available options when calling pgcli atthe terminal prompt.
In order to work it steals a couple of functions from psql, which is the postgres CLI client installed by default.
It is intended to be packaged with the debian package and to be copied on /usr/share/bash-completion/completions/pgcli (filename changes for consistency) upon installation of the package.
Please make the debian package mantainer aware of it and include it in the relevant section of the installation scripts/package.
I hope it is useful.
* deprecate Python2.7.
So we can use latest version of prompt-toolit.
Relate: https://github.com/dbcli/pgcli/pull/1149
* black format, remove 2.7 support.
* using version py35 for black.
* Revert "black format, remove 2.7 support."
This reverts commit 4b6d0496cc.
* deprecated py27 using black.
* remove 2.7 from travis.
* update setup.py: delete python 2.7 support.
* remove python3.4 support.
Python 3.4 has reached end-of-life.
https://www.python.org/downloads/release/python-340/
* drop maximun version of pytest
* update changelog
* add laixintao to contributors, delete py34 from tox
Escape then enter intended as two separate key presses is a very common
sequence when using vi mode - returning to normal mode from insert mode
(escape) and then submitting the query (enter). The presence of the
escape-enter key binding overrides this behaviour by inserting
undesirable newlines (newline is be easily inserted when in insert mode
by pressing enter) or by introducing a noticable delay/lag before enter
can be pressed after escape, due to prompt toolkit not being able to
recognise escape immediately (since it may form part of an escape-enter
sequence).