no_color
ipython
no_color | ipython | |
---|---|---|
24 | 34 | |
257 | 16,135 | |
- | 0.1% | |
8.0 | 9.6 | |
8 days ago | 6 days ago | |
HTML | Python | |
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
no_color
- Starship.rs: minimal, fast prompt for any shell
-
Unix Structured Concurrency
This sounds like a really good pattern, and something that deserves to become a modern standard (like https://no-color.org/).
I feel like this should be made opt in somehow. If you are a noninteractive process and stdin is a tty then you probably shouldn't be swallowing input. I frequently blind-type the next command while a long running command is active, because well behaved noninteractive programs don't swallow input from stdin.
- Command-line software which adds ANSI color to its output by default should check for a NO_COLOR environment variable that, when present and not an empty string (regardless of its value), prevents the addition of ANSI color.
- No_color
-
Announcing erdtree 3.0.0: A multi-threaded general purpose disk-usage and filesystem utility
Does this support the environment variable for NO_COLOR too? https://no-color.org/
- How and Why You Should Add Color to Your Scripts
-
Fulfilling a reader's request for my “dot files”
Some of us prefer tools which work best without them.
Allow me to repeat my plea for CLI developers to take a little time to read https://no-color.org and ensure their programs honor things like NO_COLOR, npm config set color false, TERM=dumb, INSIDE_EMACS etc.
https://news.ycombinator.com/item?id=35017940
-
OpenLoco Release v23.04
Change: [#1908] Detects if terminal is VT100 capable and uses colors for the output, can be disabled using NO_COLOR.
-
tint: 🌈 slog.Handler that writes tinted logs
Why not let termenv do the hard part of making this portable across terminals? It also supports lesser-known conventions like NO_COLOR.
ipython
-
The new pdbp (Pdb+) Python debugger!
If you’re already using ipython, this isn’t a problem because you’ll already need to download most of these dependencies anyway. But if you’re not using ipython… you’ll still need to download those dependencies.
-
Pandas 1.5 released
!pip install is error-prone, it is better to use %pip install, ipython even warns about this, https://github.com/ipython/ipython/pull/12954/
-
Why deprecate loading unpackaged extensions?
The git history (here is the git blame) shows it has not been updated in 9 year. Looks like a documentation issue that you should open an issue against.
-
Debugging Python programs without an IDE
Do you know IPython? It is a modern Python console that extends the capabilities of the classic builtin Python shell by offering introspection, tab completion, syntaxing coloring, as well as history. If you don't know it, I can't recommend it enough. More information can be found in its GitHub page.
-
External variables in lambda functions in Python
There is an IPython ticket on GitHub on the topic, but it's unclear if the problem has been solved.
-
Pipx: A python package consumption tool for CLI packages
For further documentation on ipython using the CLI, you can refer to the GitHub link or the documentation page.
-
Workflow-killing crash from strange added characters.
> ??????_ Traceback (most recent call last): File "/home/nvaughn4/bin/miniconda3/envs/newprime/bin/ipython", line 11, in sys.exit(start_ipython()) File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/__init__.py", line 126, in start_ipython return launch_new_instance(argv=argv, **kwargs) File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/traitlets/config/application.py", line 658, in launch_instance app.start() File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/terminal/ipapp.py", line 356, in start self.shell.mainloop() File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/terminal/interactiveshell.py", line 563, in mainloop self.interact() File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/terminal/interactiveshell.py", line 554, in interact self.run_cell(code, store_history=True) File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/core/interactiveshell.py", line 2858, in run_cell raw_cell, store_history, silent, shell_futures) File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/core/interactiveshell.py", line 2880, in _run_cell elif self.should_run_async(raw_cell): File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/core/interactiveshell.py", line 2918, in should_run_async return _should_be_async(cell) File "/home/nvaughn4/bin/miniconda3/envs/newprime/lib/python3.6/site-packages/IPython/core/async_helpers.py", line 161, in _should_be_async code = compile(cell, "<>", "exec") UnicodeEncodeError: 'utf-8' codec can't encode characters in position 537-542: surrogates not allowed If you suspect this is an IPython 7.15.0 bug, please report it at: https://github.com/ipython/ipython/issues or send an email to the mailing list at [email protected] You can print a more detailed traceback right now with "%tb", or use "%debug" to interactively debug it. Extra-detailed tracebacks for bug-reporting purposes can be enabled via: %config Application.verbose_crash=True sys:1: RuntimeWarning: coroutine 'InteractiveShell.run_cell_async' was never awaited
-
No_color
There’s one I’ve come across recently here where you’re fighting against syntax highlighting with extra error context. https://github.com/ipython/ipython/issues/13446#issuecomment...
-
Anybody else getting tired of parso and jedi?
I see. https://github.com/ipython/ipython/issues/13529
-
Django Codebase Reformatted with Black
You can automate setup for developers using this simple script:
https://github.com/ipython/ipython/pull/12091/files
And here’s a GitLab issue requesting support for blame-ignore:
https://gitlab.com/gitlab-org/gitlab/-/issues/31423
I don’t think there’s a corresponding GitHub request, but maybe if GitLab adds this feature GitHub will have some incentive to follow suit.
What are some alternatives?
pytermgui - Python TUI framework with mouse support, modular widget system, customizable and rapid terminal markup language and more!
CPython - The Python programming language
Clipboard - 😎🏖️🐬 Your new, 𝙧𝙞𝙙𝙤𝙣𝙠𝙪𝙡𝙞𝙘𝙞𝙤𝙪𝙨𝙡𝙮 smart clipboard manager
bpython - bpython - A fancy curses interface to the Python interactive interpreter
emacs-theme-gruvbox - Gruvbox is a retro groove color scheme for Emacs. Port of the Vim version.
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
no-ansi - A single-function CLI tool to strip escape codes from input
vim-slime - A vim plugin to give you some slime. (Emacs)
gofx - 🐾 fx-like command-line JSON processing tool
spacemacs - A community-driven Emacs distribution - The best editor is neither Emacs nor Vim, it's Emacs *and* Vim!
grc - generic colouriser
ptpython - A better Python REPL