Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2026-03-21 15:45
📄 INSTALLER pip	4 B	2026-01-20 12:58
📄 LICENSE GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.	7.46 KB	2026-01-20 12:58
📄 METADATA Metadata-Version: 2.1 Name: autocommand Version: 2.2.2 Summary: A library to create a command-line program from a function Home-page: https://github.com/Lucretiel/autocommand Author: Nathan West License: LGPLv3 Project-URL: Homepage, https://github.com/Lucretiel/autocommand Project-URL: Bug Tracker, https://github.com/Lucretiel/autocommand/issues Platform: any Classifier: Development Status :: 6 - Mature Classifier: Intended Audience :: Developers Classifier: License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) Classifier: Programming Language :: Python Classifier: Programming Language :: Python :: 3 Classifier: Programming Language :: Python :: 3 :: Only Classifier: Topic :: Software Development Classifier: Topic :: Software Development :: Libraries Classifier: Topic :: Software Development :: Libraries :: Python Modules Requires-Python: >=3.7 Description-Content-Type: text/markdown License-File: LICENSE [![PyPI version](https://badge.fury.io/py/autocommand.svg)](https://badge.fury.io/py/autocommand) # autocommand A library to automatically generate and run simple argparse parsers from function signatures. ## Installation Autocommand is installed via pip: ``` $ pip install autocommand ``` ## Usage Autocommand turns a function into a command-line program. It converts the function's parameter signature into command-line arguments, and automatically runs the function if the module was called as `__main__`. In effect, it lets your create a smart main function. ```python from autocommand import autocommand # This program takes exactly one argument and echos it. @autocommand(__name__) def echo(thing): print(thing) ``` ``` $ python echo.py hello hello $ python echo.py -h usage: echo [-h] thing positional arguments: thing optional arguments: -h, --help show this help message and exit $ python echo.py hello world # too many arguments usage: echo.py [-h] thing echo.py: error: unrecognized arguments: world ``` As you can see, autocommand converts the signature of the function into an argument spec. When you run the file as a program, autocommand collects the command-line arguments and turns them into function arguments. The function is executed with these arguments, and then the program exits with the return value of the function, via `sys.exit`. Autocommand also automatically creates a usage message, which can be invoked with `-h` or `--help`, and automatically prints an error message when provided with invalid arguments. ### Types You can use a type annotation to give an argument a type. Any type (or in fact any callable) that returns an object when given a string argument can be used, though there are a few special cases that are described later. ```python @autocommand(__name__) def net_client(host, port: int): ... ``` Autocommand will catch `TypeErrors` raised by the type during argument parsing, so you can supply a callable and do some basic argument validation as well. ### Trailing Arguments You can add a `args` parameter to your function to give it trailing arguments. The command will collect 0 or more trailing arguments and supply them to `args` as a tuple. If a type annotation is supplied, the type is applied to each argument. ```python # Write the contents of each file, one by one @autocommand(__name__) def cat(files): for filename in files: with open(filename) as file: for line in file: print(line.rstrip()) ``` ``` $ python cat.py -h usage: ipython [-h] [file [file ...]] positional arguments: file optional arguments: -h, --help show this help message and exit ``` ### Options To create `--option` switches, just assign a default. Autocommand will automatically create `--long` and `-s`hort switches. ```python @autocommand(__name__) def do_with_config(argument, config='~/foo.conf'): pass ``` ``` $ python example.py -h usage: example.py [-h] [-c CONFIG] argument positional arguments: argument optional arguments: -h, --help show this help message and exit -c CONFIG, --config CONFIG ``` The option's type is automatically deduced from the default, unless one is explicitly given in an annotation: ```python @autocommand(__name__) def http_connect(host, port=80): print('{}:{}'.format(host, port)) ``` ``` $ python http.py -h usage: http.py [-h] [-p PORT] host positional arguments: host optional arguments: -h, --help show this help message and exit -p PORT, --port PORT $ python http.py localhost localhost:80 $ python http.py localhost -p 8080 localhost:8080 $ python http.py localhost -p blah usage: http.py [-h] [-p PORT] host http.py: error: argument -p/--port: invalid int value: 'blah' ``` #### None If an option is given a default value of `None`, it reads in a value as normal, but supplies `None` if the option isn't provided. #### Switches If an argument is given a default value of `True` or `False`, or given an explicit `bool` type, it becomes an option switch. ```python @autocommand(__name__) def example(verbose=False, quiet=False): pass ``` ``` $ python example.py -h usage: example.py [-h] [-v] [-q] optional arguments: -h, --help show this help message and exit -v, --verbose -q, --quiet ``` Autocommand attempts to do the "correct thing" in these cases- if the default is `True`, then supplying the switch makes the argument `False`; if the type is `bool` and the default is some other `True` value, then supplying the switch makes the argument `False`, while not supplying the switch makes the argument the default value. Autocommand also supports the creation of switch inverters. Pass `add_nos=True` to `autocommand` to enable this. ``` @autocommand(__name__, add_nos=True) def example(verbose=False): pass ``` ``` $ python example.py -h usage: ipython [-h] [-v] [--no-verbose] optional arguments: -h, --help show this help message and exit -v, --verbose --no-verbose ``` Using the `--no-` version of a switch will pass the opposite value in as a function argument. If multiple switches are present, the last one takes precedence. #### Files If the default value is a file object, such as `sys.stdout`, then autocommand just looks for a string, for a file path. It doesn't do any special checking on the string, though (such as checking if the file exists); it's better to let the client decide how to handle errors in this case. Instead, it provides a special context manager called `smart_open`, which behaves exactly like `open` if a filename or other openable type is provided, but also lets you use already open files: ```python from autocommand import autocommand, smart_open import sys # Write the contents of stdin, or a file, to stdout @autocommand(__name__) def write_out(infile=sys.stdin): with smart_open(infile) as f: for line in f: print(line.rstrip()) # If a file was opened, it is closed here. If it was just stdin, it is untouched. ``` ``` $ echo "Hello World!" \| python write_out.py \| tee hello.txt Hello World! $ python write_out.py --infile hello.txt Hello World! ``` ### Descriptions and docstrings The `autocommand` decorator accepts `description` and `epilog` kwargs, corresponding to the `description <https://docs.python.org/3/library/argparse.html#description>`_ and `epilog <https://docs.python.org/3/library/argparse.html#epilog>`_ of the `ArgumentParser`. If no description is given, but the decorated function has a docstring, then it is taken as the `description` for the `ArgumentParser`. You can also provide both the description and epilog in the docstring by splitting it into two sections with 4 or more - characters. ```python @autocommand(__name__) def copy(infile=sys.stdin, outfile=sys.stdout): ''' Copy an the contents of a file (or stdin) to another file (or stdout) ---------- Some extra documentation in the epilog ''' with smart_open(infile) as istr: with smart_open(outfile, 'w') as ostr: for line in istr: ostr.write(line) ``` ``` $ python copy.py -h usage: copy.py [-h] [-i INFILE] [-o OUTFILE] Copy an the contents of a file (or stdin) to another file (or stdout) optional arguments: -h, --help show this help message and exit -i INFILE, --infile INFILE -o OUTFILE, --outfile OUTFILE Some extra documentation in the epilog $ echo "Hello World" \| python copy.py --outfile hello.txt $ python copy.py --infile hello.txt --outfile hello2.txt $ python copy.py --infile hello2.txt Hello World ``` ### Parameter descriptions You can also attach description text to individual parameters in the annotation. To attach both a type and a description, supply them both in any order in a tuple ```python @autocommand(__name__) def copy_net( infile: 'The name of the file to send', host: 'The host to send the file to', port: (int, 'The port to connect to')): ''' Copy a file over raw TCP to a remote destination. ''' # Left as an exercise to the reader ``` ### Decorators and wrappers Autocommand automatically follows wrapper chains created by `@functools.wraps`. This means that you can apply other wrapping decorators to your main function, and autocommand will still correctly detect the signature. ```python from functools import wraps from autocommand import autocommand def print_yielded(func): ''' Convert a generator into a function that prints all yielded elements ''' @wraps(func) def wrapper(args, kwargs): for thing in func(args, kwargs): print(thing) return wrapper @autocommand(__name__, description= 'Print all the values from START to STOP, inclusive, in steps of STEP', epilog= 'STOP and STEP default to 1') @print_yielded def seq(stop, start=1, step=1): for i in range(start, stop + 1, step): yield i ``` ``` $ seq.py -h usage: seq.py [-h] [-s START] [-S STEP] stop Print all the values from START to STOP, inclusive, in steps of STEP positional arguments: stop optional arguments: -h, --help show this help message and exit -s START, --start START -S STEP, --step STEP STOP and STEP default to 1 ``` Even though autocommand is being applied to the `wrapper` returned by `print_yielded`, it still retreives the signature of the underlying `seq` function to create the argument parsing. ### Custom Parser While autocommand's automatic parser generator is a powerful convenience, it doesn't cover all of the different features that argparse provides. If you need these features, you can provide your own parser as a kwarg to `autocommand`: ```python from argparse import ArgumentParser from autocommand import autocommand parser = ArgumentParser() # autocommand can't do optional positonal parameters parser.add_argument('arg', nargs='?') # or mutually exclusive options group = parser.add_mutually_exclusive_group() group.add_argument('-v', '--verbose', action='store_true') group.add_argument('-q', '--quiet', action='store_true') @autocommand(__name__, parser=parser) def main(arg, verbose, quiet): print(arg, verbose, quiet) ``` ``` $ python parser.py -h usage: write_file.py [-h] [-v \| -q] [arg] positional arguments: arg optional arguments: -h, --help show this help message and exit -v, --verbose -q, --quiet $ python parser.py None False False $ python parser.py hello hello False False $ python parser.py -v None True False $ python parser.py -q None False True $ python parser.py -vq usage: parser.py [-h] [-v \| -q] [arg] parser.py: error: argument -q/--quiet: not allowed with argument -v/--verbose ``` Any parser should work fine, so long as each of the parser's arguments has a corresponding parameter in the decorated main function. The order of parameters doesn't matter, as long as they are all present. Note that when using a custom parser, autocommand doesn't modify the parser or the retrieved arguments. This means that no description/epilog will be added, and the function's type annotations and defaults (if present) will be ignored. ## Testing and Library use The decorated function is only called and exited from if the first argument to `autocommand` is `'__main__'` or `True`. If it is neither of these values, or no argument is given, then a new main function is created by the decorator. This function has the signature `main(argv=None)`, and is intended to be called with arguments as if via `main(sys.argv[1:])`. The function has the attributes `parser` and `main`, which are the generated `ArgumentParser` and the original main function that was decorated. This is to facilitate testing and library use of your main. Calling the function triggers a `parse_args()` with the supplied arguments, and returns the result of the main function. Note that, while it returns instead of calling `sys.exit`, the `parse_args()` function will raise a `SystemExit` in the event of a parsing error or `-h/--help` argument. ```python @autocommand() def test_prog(arg1, arg2: int, quiet=False, verbose=False): if not quiet: print(arg1, arg2) if verbose: print("LOUD NOISES") return 0 print(test_prog(['-v', 'hello', '80'])) ``` ``` $ python test_prog.py hello 80 LOUD NOISES 0 ``` If the function is called with no arguments, `sys.argv[1:]` is used. This is to allow the autocommand function to be used as a setuptools entry point. ## Exceptions and limitations - There are a few possible exceptions that `autocommand` can raise. All of them derive from `autocommand.AutocommandError`. - If an invalid annotation is given (that is, it isn't a `type`, `str`, `(type, str)`, or `(str, type)`, an `AnnotationError` is raised. The `type` may be any callable, as described in the `Types`_ section. - If the function has a `kwargs` parameter, a `KWargError` is raised. - If, somehow, the function has a positional-only parameter, a `PositionalArgError` is raised. This means that the argument doesn't have a name, which is currently not possible with a plain `def` or `lambda`, though many built-in functions have this kind of parameter. - There are a few argparse features that are not supported by autocommand. - It isn't possible to have an optional positional argument (as opposed to a `--option`). POSIX thinks this is bad form anyway. - It isn't possible to have mutually exclusive arguments or options - It isn't possible to have subcommands or subparsers, though I'm working on a few solutions involving classes or nested function definitions to allow this. ## Development Autocommand cannot be important from the project root; this is to enforce separation of concerns and prevent accidental importing of `setup.py` or tests. To develop, install the project in editable mode: ``` $ python setup.py develop ``` This will create a link to the source files in the deployment directory, so that any source changes are reflected when it is imported.	14.65 KB	2026-01-20 12:58
📄 RECORD autocommand-2.2.2.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4 autocommand-2.2.2.dist-info/LICENSE,sha256=reeNBJgtaZctREqOFKlPh6IzTdOFXMgDSOqOJAqg3y0,7634 autocommand-2.2.2.dist-info/METADATA,sha256=OADZuR3O6iBlpu1ieTgzYul6w4uOVrk0P0BO5TGGAJk,15006 autocommand-2.2.2.dist-info/RECORD,, autocommand-2.2.2.dist-info/WHEEL,sha256=2wepM1nk4DS4eFpYrW1TTqPcoGNfHhhO_i5m4cOimbo,92 autocommand-2.2.2.dist-info/top_level.txt,sha256=AzfhgKKS8EdAwWUTSF8mgeVQbXOY9kokHB6kSqwwqu0,12 autocommand/__init__.py,sha256=zko5Rnvolvb-UXjCx_2ArPTGBWwUK5QY4LIQIKYR7As,1037 autocommand/__pycache__/__init__.cpython-312.pyc,, autocommand/__pycache__/autoasync.cpython-312.pyc,, autocommand/__pycache__/autocommand.cpython-312.pyc,, autocommand/__pycache__/automain.cpython-312.pyc,, autocommand/__pycache__/autoparse.cpython-312.pyc,, autocommand/__pycache__/errors.cpython-312.pyc,, autocommand/autoasync.py,sha256=AMdyrxNS4pqWJfP_xuoOcImOHWD-qT7x06wmKN1Vp-U,5680 autocommand/autocommand.py,sha256=hmkEmQ72HtL55gnURVjDOnsfYlGd5lLXbvT4KG496Qw,2505 autocommand/automain.py,sha256=A2b8i754Mxc_DjU9WFr6vqYDWlhz0cn8miu8d8EsxV8,2076 autocommand/autoparse.py,sha256=WVWmZJPcbzUKXP40raQw_0HD8qPJ2V9VG1eFFmmnFxw,11642 autocommand/errors.py,sha256=7aa3roh9Herd6nIKpQHNWEslWE8oq7GiHYVUuRqORnA,886	1.28 KB	2026-01-20 12:58
📄 WHEEL Wheel-Version: 1.0 Generator: bdist_wheel (0.38.4) Root-Is-Purelib: true Tag: py3-none-any	92 B	2026-01-20 12:58
📄 top_level.txt autocommand	12 B	2026-01-20 12:58

Terminal