The args and options help for a nested command only gets displayed by --help if the parent commands have their args filled. That is a shortcoming of the module.
to double up, just use function-chaining. Put your logic in a separate utility function. This way, you can add it to as many groups as you want; each gets its own function, but they all just call your utility function. Less code reuse.
Good video, thx! But also funny as you are explaining a cmdline/parameterization module for Python while demonstrating/running it in a shell that offers all this by default: PowerShell. Of course, I know Python is more general purpose and has somewhat prettier/stricter code, but PS is actually very similar in code/learning while also having some great unique features besides the object pipeline, like: smart-aliasing, abstract syntax tree and extensible type system.
@@jasperzanjani Mostly true. Python is very popular for many reasons/purposes. PowerShell is a very powerful shell, cross platform. Linux/mac admins are used to pipe/parse strings, as everything is basically a file. But the world has moved on and is bigger than just Windows...with Web, API's, databases, xml/json, etc... Bash by itself is not sufficient anymore without external cmdline tools (that can be written with Python). However, piping objects on the cmdline is a lot more powerful. Bash/Python doesn't do that.
Helpful video, thanks Jasper! Regards from India
This was helpful seeing the groups actually coded out. It wasn't very well-documented. Appreciated!
The args and options help for a nested command only gets displayed by --help if the parent commands have their args filled. That is a shortcoming of the module.
Thanks! You had an excellent presentation. You need more subs, brotha.
how clear course！Solved a problem that had been puzzling me for a long time!
Great video dude!! Also, can you please link the wallpaper!!!??? It looks sick!!!
Excelent video, thank you!
Excellent Explanation, please seed more informations like that in the World
Very informative. Thank you
to double up, just use function-chaining. Put your logic in a separate utility function. This way, you can add it to as many groups as you want; each gets its own function, but they all just call your utility function. Less code reuse.
I know some of those words
Thank you for the video. It was a great and simple intro!
Great.., thank you so much 😊
Awesome videos bro 😎
Thanks. Cool video
good work bro ,,, enjoyed it and learned from it a lot
Thank you sir. Big help.
Great tutorial, thanks
Can you elaborate on how options are used. eg: rm -rf [dir-name] how would you implement -rf?
thank u
Good video, thx! But also funny as you are explaining a cmdline/parameterization module for Python while demonstrating/running it in a shell that offers all this by default: PowerShell. Of course, I know Python is more general purpose and has somewhat prettier/stricter code, but PS is actually very similar in code/learning while also having some great unique features besides the object pipeline, like: smart-aliasing, abstract syntax tree and extensible type system.
nobody uses PowerShell except for Windows admins
@@jasperzanjani Mostly true. Python is very popular for many reasons/purposes. PowerShell is a very powerful shell, cross platform. Linux/mac admins are used to pipe/parse strings, as everything is basically a file. But the world has moved on and is bigger than just Windows...with Web, API's, databases, xml/json, etc... Bash by itself is not sufficient anymore without external cmdline tools (that can be written with Python). However, piping objects on the cmdline is a lot more powerful. Bash/Python doesn't do that.
Thank you
thx.
Irani?
koskeshi?
15m36s "clee"