PSHELL3(1)

πŸ“¦
version 2.0.2 Β· 5 versions
, in debian trixie, ubuntu resolute

πŸ’– PSHELL3 πŸ’–

okay bestie, gather round, because this is the pshell3 manual page and she is serving ✨ (she lives in section 1 of the manual, aka User Commands, if you were wondering where to find her 🫢)


🌸 NAME 🌸

pshell3 β€” the Python 3 Pyramid command. that's it, that's the name, she's iconic, periodt πŸ‘‘


✨ DESCRIPTION ✨

so basically here's the whole vibe, and yes I'm giving you the usage line verbatim because I do not play about syntax:

usage: pshell3 [-h] [-p PYTHON_SHELL] [-l] [--setup SETUP]

       [config_uri] [config_vars ...]

What she does: she opens up an interactive shell with a Pyramid app already loaded inside it. no cap, that's the whole point of her existence πŸ’…

She takes one positional argument called config_uri, and that lil guy tells her which PasteDeploy config file to use for the interactive shell. The format is:

inifile#name

If you leave the name off? No stress, she'll just assume the Pyramid default application. Example time, look at her go:

pshell myapp.ini#main

Now here's the part where she's lowkey a detective πŸ” β€” if you don't point the loader directly at the section of the ini file that contains your Pyramid application, she will go and try to find the app for you herself. main character energy fr fr.

And if you're loading a pipeline that has more than one Pyramid application inside it, the loader will use the last one. that's just the rule, don't fight it πŸ™ˆ


πŸŽ€ positional arguments πŸŽ€

  • config_uri β€” the URI to the configuration file. that's the file, that's the address, that's her whole starting point πŸ—ΊοΈ
  • config_vars β€” variables that the config file needs, bestie. For example, http_port=%(http_port)s would expect http_port=8080 to be passed here. she's like "give me the value or the placeholder stays empty" 😭

πŸ’… options πŸ’…

  • -h, --help β€” shows this help message and then dips, exits, gone, bye πŸ‘‹
  • -p PYTHON_SHELL, --python-shell PYTHON_SHELL β€” pick which shell you wanna use. wanna know your options? that's literally what the --list-shells option is for, go look πŸ‘€
  • -l, --list-shells β€” lists all the available shells. all of them. every single one. she's thorough like that πŸ’–
  • --setup SETUP β€” a callable that gets passed the environment before it's made available to the shell. and heads up: this option will override the 'setup' key in the [pshell] ini section. so if you set both, this one wins, no arguing 🫢
ngl the --setup override is the kind of thing that will sneak up on you, so if your ini [pshell] setup key suddenly seems ignored… it's not haunted, you just passed --setup πŸ’€

and that's the whole page, you're welcome, I love you, go run some shells 🐚

kisses, this has been pshell3 version 2.0.2+dfsg-1 from December 2024 β€” see you next read, mwah πŸ’‹βœ¨πŸŽ€

πŸ“¦ where this page comes from