typer
runtimelab
Our great sponsors
typer | runtimelab | |
---|---|---|
86 | 51 | |
13,353 | 1,323 | |
- | 1.6% | |
6.7 | 5.1 | |
2 days ago | about 22 hours ago | |
Python | ||
MIT License | MIT 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.
typer
- Copilot for your GitHub stars
-
Things I've learned about building CLI tools in Python
I have been using Typer on every one of my CLI projects which uses Click under the hood. The documentation is fantastic, the CLI app it produces looks great and lets you create things quickly. I high recommend it.
-
Things to do with standalone script
Adding CLI capabilities. My preferred library here is typer.
-
The different uses of Python type hints
Similarly for Typer, which is literally "the FastAPI of CLIs"[1]. Handy to type your `main` parameters and have CLI argument parsing. For more complicated cases, it's a wrapper around Click.
-
Command line parser library, which one do you like the most, regardless of language?
interesting that you hate python, but love Click. Did you try Typer which uses Click underneath?
-
I made a file manager in python
Try to make it into a command line tool? check https://typer.tiangolo.com/ for example
- How does "python3 *file* -*letter* work?
-
How to make a CLI?
I used this template repo to make a bash cli https://github.com/SierraSoftworks/bash-cli then I made a brew formula to make it installable. It provide a nice way to make a cli with nested commands like git. As others mentioned other languages like python have great support for making nice clis see https://typer.tiangolo.com/ for an example framework in python. I chose bash because packaging a python cli for a private brew package is a pain and 99% of what I needed the cli to do was inkoke other clis, so bash made sense for my case.
-
I am sick of writing argparse boilerplate code, so I made "duckargs" to do it for me
Very cool. Iβve been using Typer lately. Easy to give a library a cli without too much boilerplate.
-
Just released my much-improved YouTube archiver as v1.2 ππ
Check out Typer for the command line tooling, might make it a bit easier to maintain later on!
runtimelab
-
Why choose async/await over threads?
Experiment result write-up: https://github.com/dotnet/runtimelab/blob/e69dda51c7d796b812...
TLDR: The green threads experiment was a failure as it found (expected and obvious) issues that the Java applications are now getting to enjoy, joining their Go colleagues, while also requiring breaking changes. It, however, gave inspiration to subsequent re-examination of current async/await implementation and whether it can be improved by moving state machine generation and execution away from IL completely to runtime. It was a massive success as evidenced by preliminary overhead estimations in the results.
-
Garnet β A new remote cache-store from Microsoft Research
Yeah, it kind of is. There are quite a few of experiments that are conducted to see if they show promise in the prototype form and then are taken further for proper integration if they do.
Unfortunately, object stack allocation was not one of them even though DOTNET_JitObjectStackAllocation configuration knob exists today, enabling it makes zero impact as it almost never kicks in. By the end of the experiment[0], it was concluded that before investing effort in this kind of feature becomes profitable given how a lot of C# code is written, there are many other lower hanging fruits.
To contrast this, in continuation to green threads experiment, a runtime handled tasks experiment[1] which moves async state machine handling from IL emitted by Roslyn to special-cased methods and then handling purely in runtime code has been a massive success and is now being worked on to be integrated in one of the future version of .NET (hopefully 10?)
[0] https://github.com/dotnet/runtime/issues/11192
[1] https://github.com/dotnet/runtimelab/blob/feature/async2-exp...
-
JEP Draft β Derived Record Creation (Preview) β Java
The only way to avoid it is to not build on top of Java or not adding any features on top of Java.
> To give another example with C#, there has been a lot of recent discussion about finding potential alternatives to their async-await concurrency model. They cite the level of effort it takes to maintain the async await style code and the costs that come from this.
I had a very different take-away. They did PoC with virtual threads and decided it's not worth the switch now and async-await that they have is good enough.
https://github.com/dotnet/runtimelab/issues/2398
> Some of the languages it gets compared too aren't even that old yet.
C# is old enough to drink and Scala just had its 20th birthday this week :)
-
.NET 8 β .NET Blog
It was tried and the dotnet team decided to drop it: https://github.com/dotnet/runtimelab/issues/2398
-
.NET Green Thread Experiment Results
Technical details here: https://github.com/dotnet/runtimelab/blob/feature/green-thre...
-
Thread-per-Core
Just last month .NET ended a green threading experiment, mainly because the overhead it adds to FFI was too high:
https://github.com/dotnet/runtimelab/issues/2398
Rust had green threads until late 2014, and they were removed because of their impact on performance.
Everyone has done the basic research: green threading is a convenient abstraction that comes with certain performance trade offs. It doesn't work for the kind of profile that Rust is trying to target.
- Java 21 makes me like Java again
-
The compact overview of JDK 21βs βfrozenβ feature list
Green Threads Experiment if anyone is interested in what they've done in .NET: https://github.com/dotnet/runtimelab/issues/2057
Personally Asyc/Await is the only thing keeping me from the C# ecosystem.
-
Question about NativeAOT platform support
There is a compiler being developed by the community (which is experimental and not supported by Microsoft) which supports full AOT: https://github.com/dotnet/runtimelab/tree/feature/NativeAOT-LLVM
What are some alternatives?
click - Python composable command line interface toolkit
Python Fire - Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object.
Gooey - Turn (almost) any Python command line program into a full GUI application with one line
rich - Rich is a Python library for rich text and beautiful formatting in the terminal.
python-prompt-toolkit - Library for building powerful interactive command line applications in Python
cement - Application Framework for Python
docopt - Pythonic command line arguments parser, that will make you smile
clint - Python Command-line Application Tools
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
cliff - Command Line Interface Formulation Framework. Mirror of code maintained at opendev.org.
asciimatics - A cross platform package to do curses-like operations, plus higher level APIs and widgets to create text UIs and ASCII art animations
Argh - An argparse wrapper that doesn't make you say "argh" each time you deal with it.