prompt_toolkit
is a library for building powerful interactive command lines
and terminal applications in Python.
Read the documentation on readthedocs.
ptpython is an interactive Python Shell, build on top of prompt_toolkit.
prompt_toolkit
could be a replacement for GNU readline, but it can be much
more than that.
Some features:
Feel free to create tickets for bugs and feature requests, and create pull requests if you have nice patches that you would like to share with others.
prompt_toolkit
is cross platform, and everything that you build on top
should run fine on both Unix and Windows systems. On Windows, it uses a
different event loop (WaitForMultipleObjects
instead of select
), and
another input and output system. (Win32 APIs instead of pseudo-terminals and
VT100.)
It's worth noting that the implementation is a "best effort of what is possible". Both Unix and Windows terminals have their limitations. But in general, the Unix experience will still be a little better.
For Windows, it's recommended to use either cmder or conemu.
pip install prompt_toolkit
For Conda, do:
conda install -c https://conda.anaconda.org/conda-forge prompt_toolkit
The most simple example of the library would look like this:
from prompt_toolkit import prompt
if __name__ == '__main__':
answer = prompt('Give me some input: ')
print('You said: %s' % answer)
For more complex examples, have a look in the examples
directory. All
examples are chosen to demonstrate only one thing. Also, don't be afraid to
look at the source code. The implementation of the prompt
function could be
a good start.
Note for Python 2: all strings are expected to be unicode strings. So, either
put a small u
in front of every string or put from __future__ import
unicode_literals
at the start of the above example.
Shells:
Full screen applications:
(Want your own project to be listed here? Please create a GitHub issue.)
The source code of prompt_toolkit
should be readable, concise and
efficient. We prefer short functions focussing each on one task and for which
the input and output types are clearly specified. We mostly prefer composition
over inheritance, because inheritance can result in too much functionality in
the same object. We prefer immutable objects where possible (objects don't
change after initialisation). Reusability is important. We absolutely refrain
from having a changing global state, it should be possible to have multiple
independent instances of the same code in the same process. The architecture
should be layered: the lower levels operate on primitive operations and data
structures giving -- when correctly combined -- all the possible flexibility;
while at the higher level, there should be a simpler API, ready-to-use and
sufficient for most use cases. Thinking about algorithms and efficiency is
important, but avoid premature optimization.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。