PYTHON(1)

๐Ÿ“ฆ
version 3.14.10 ยท 6 versions
, in alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, fedora 43, fedora 44, nixpkgs unstable

PYTHON(1) ๐Ÿ’…

okay bestie, welcome to the General Commands Manual for python. buckle up, this one's a whole personality ๐ŸŽ€


โœจ NAME โœจ

python โ€” an interpreted, interactive, object-oriented programming language ๐Ÿ๐Ÿ’–

yes that's the whole thing. she's a language, she interprets, she interacts, she's object-oriented, she ate.


๐ŸŒธ SYNOPSIS ๐ŸŒธ

python [ -B ] [ -b ] [ -d ] [ -E ] [ -h ] [ -i ] [ -I ]
       [ -m module-name ] [ -q ] [ -R ] [ -O ] [ -OO ] [ -P ] [ -s ] [ -S ] [ -u ]
       [ -v ] [ -V ] [ -W argument ] [ -x ] [ -X option ] [ -?  ]
       [ --check-hash-based-pycs default | always | never ]
       [ --help ] [ --help-env ] [ --help-xoptions ] [ --help-all ]
       [ -c command | script | - ] [ arguments ]

it's giving "the whole alphabet walked in and sat down" ngl. every single one of those is explained below, no skips, no shortcuts ๐Ÿซถ


๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

Python is an interpreted, interactive, object-oriented programming language that combines remarkable power with very clear syntax. iconic combo honestly โ€” like being both gorgeous and smart ๐Ÿ’…โœจ

For an intro to programming in Python, go peek at the Python Tutorial. The Python Library Reference is where you'll find the built-in and standard types, constants, functions and modules all documented. And finally, the Python Reference Manual describes the syntax and semantics of the core language in โ€” and I quote, bestie โ€” (perhaps too) much detail ๐Ÿ˜ญ. These documents can be found via the INTERNET RESOURCES below, and they might already be installed on your system too, no biggie.


Python's basic power can be extended with your own modules written in C or C++ ๐Ÿ”ฅ. On most systems, those modules can be dynamically loaded. Python is also adaptable as an extension language for existing applications โ€” see the internal documentation for hints, iykyk ๐Ÿ‘‘


Want to read docs for installed Python modules and packages? Just run the pydoc program. that's it. that's the tip. ๐ŸŒˆ

more parts coming bestie, don't go anywhere ๐Ÿ’œ

โœจ COMMAND LINE OPTIONS โœจ

Okay bestie, this is the part where the real fun starts โ€” every single flag you can throw at python3. Grab a snack, we're going through all of them. ๐Ÿ“

  • -B โ€” bestie do NOT write .pyc files on import. That's it, that's the whole vibe. (Also peep PYTHONDONTWRITEBYTECODE if you want this energy everywhere.)
  • -b โ€” throws warnings at you about str(bytes_instance), str(bytearray_instance), and comparing bytes/bytearray with str. Add another one โ€” -bb โ€” and it stops being a warning and becomes a whole error. Glow up. ๐Ÿ’…
  • -c command โ€” run the command you type in here (more on that in the next section, iykyk). Heads up: this ends the option list, so everything after it gets passed as arguments to your command. Lowkey important.
  • --check-hash-based-pycs mode โ€” controls how Python decides whether hash-based .pyc files are up to date. Vibe check for your bytecode, basically.
  • -d โ€” turns on parser debugging output. Experts only, and only if your build even has it compiled in. Not for the faint of heart fr.
  • -E โ€” ignore environment variables like PYTHONPATH and PYTHONHOME that mess with how the interpreter behaves. Boundaries, periodt.
  • -h, -?, --help โ€” prints the usage for the interpreter executable and dips. Classic.
  • --help-env โ€” prints help about Python-specific environment variables and exits. ๐Ÿงš
  • --help-xoptions โ€” prints help about implementation-specific -X options and exits.
  • --help-all โ€” prints the complete usage information and exits. The full lore drop.
  • -i โ€” when a script is passed as the first argument, or you used -c, this drops you into interactive mode after the script or command runs. It does not read the $PYTHONSTARTUP file. Absolute lifesaver for inspecting global variables or getting a stack trace when a script raises an exception. ๐Ÿ‘‘
  • -I โ€” isolated mode, babes. This implies -E, -P and -s. In isolated mode, sys.path contains neither the script's directory nor the user's site-packages directory. All PYTHON* environment variables are ignored too. And honestly? Further restrictions may be imposed to stop the user from injecting malicious code. She's locked down. ๐Ÿ”ฅ
  • -m module-name โ€” searches sys.path for the module you named and runs the matching .py file as a script. Just like -c, this terminates the option list โ€” everything after gets passed as arguments to the module.
  • -O โ€” removes assert statements and any code conditional on the value of __debug__; it also augments the filename for compiled (bytecode) files by adding .opt-1 before the .pyc extension.
  • -OO โ€” does everything -O does AND discards docstrings; changes the compiled (bytecode) filename by adding .opt-2 before the .pyc extension. Double stripped. ๐Ÿ’€
  • -P โ€” don't automatically prepend a potentially unsafe path to sys.path, like the current directory, the script's directory, or an empty string. See also the PYTHONSAFEPATH environment variable.
  • -q โ€” do not print the version and copyright messages. (They're suppressed in non-interactive mode anyway, so consider this your quiet luxury era.)
  • -R โ€” turn on hash randomization. Ngl this only does anything if PYTHONHASHSEED is set to 0, because hash randomization is already enabled by default. Iconic but mostly ceremonial.
  • -s โ€” don't add the user site directory to sys.path.
  • -S โ€” disable the import of the module site and the site-dependent manipulations of sys.path that come with it. And yes, it also disables those manipulations if site gets explicitly imported later.
  • -u โ€” force the stdout and stderr streams to be unbuffered. Quick note: this has no effect on the stdin stream.
  • -v โ€” prints a message every time a module is initialized, showing the place (filename or built-in module) from which it's loaded. Give it twice and you get a message for every single file checked while searching for a module. It also spills the tea on module cleanup at exit. So chatty, we love her. ๐Ÿซถ
  • -V, --version โ€” prints the Python version number of the executable and exits. Give it twice and you get more information about the build.
  • -W argument โ€” warning control. Python's warning machinery by default prints warning messages to sys.stderr.

The simplest settings apply a particular action unconditionally to all warnings emitted by a process (even those that are otherwise ignored by default):

-Wdefault  # Warn once per call location
-Werror    # Convert to exceptions
-Walways   # Warn every time
-Wall      # Same as -Walways
-Wmodule   # Warn once per calling module
-Wonce     # Warn once per Python process
-Wignore   # Never warn

The action names can be abbreviated however you want and the interpreter will resolve them to the appropriate action name. For example, -Wi is the same as -Wignore.

The full form of argument is:

action:message:category:module:lineno

Empty fields match all values; trailing empty fields may be omitted. For example -W ignore::DeprecationWarning ignores all DeprecationWarning warnings.

The action field is as explained above but only applies to warnings that match the remaining fields.

The message field must match the start of the warning message; this match is case-insensitive.

The category field matches the warning category (ex: "DeprecationWarning"). This must be a class name; the match tests whether the actual warning category of the message is a subclass of the specified warning category.

The module field matches the (fully-qualified) module name; this match is case-sensitive.

The lineno field matches the line number, where zero matches all line numbers and is thus equivalent to an omitted line number.

Multiple -W options can be given; when a warning matches more than one option, the action for the last matching option is performed. Invalid -W options are ignored (though, a warning message is printed about invalid options when the first warning is issued).

Warnings can also be controlled using the PYTHONWARNINGS environment variable and from within a Python program using the warnings module. For example, the warnings.filterwarnings() function can be used to use a regular expression on the warning message.

  • -X option โ€” set an implementation-specific option. The following options are available:
    • -X cpu_count=N โ€” override the return value of os.cpu_count(). -X cpu_count=default cancels the overriding. See also PYTHON_CPU_COUNT.
    • -X dev โ€” enable CPython's "development mode", introducing additional runtime checks that are too expensive to be on by default. It will not be more verbose than the default if the code is correct: new warnings are only emitted when an issue is detected. Effect of the developer mode:
      • Add default warning filter, as -W default.
      • Install debug hooks on memory allocators: see the PyMem_SetupDebugHooks() C function.
      • Enable the faulthandler module to dump the Python traceback on a crash.
      • Enable asyncio debug mode.
      • Set the dev_mode attribute of sys.flags to True.
      • io.IOBase destructor logs close() exceptions.
    • -X importtime โ€” show how long each import takes. It shows module name, cumulative time (including nested imports) and self time (excluding nested imports). Note that its output may be broken in multi-threaded application. Typical usage is python3 -X importtime -c 'import asyncio'.

-X importtime=2 enables additional output that indicates when an imported module has already been loaded. In such cases, the string cached will be printed in both time columns.

  • -X faulthandler โ€” enable faulthandler.
  • -X frozen_modules=[on|off] โ€” whether or not frozen modules should be used. The default is "on" (or "off" if you are running a local build).
  • -X gil=[0|1] โ€” enable (1) or disable (0) the GIL. See also PYTHON_GIL. Only available in builds configured with --disable-gil.
  • -X int_max_str_digits=number โ€” limit the size of intโ†”str conversions. This helps avoid denial of service attacks when parsing untrusted data. The default is sys.int_info.default_max_str_digits. 0 disables.
  • -X no_debug_ranges โ€” disable the inclusion of the tables mapping extra location information (end line, start column offset and end column offset) to every instruction in code objects. This is useful when smaller code objects and pyc files are desired, as well as suppressing the extra visual location indicators when the interpreter displays tracebacks.
  • -X perf โ€” support the Linux "perf" profiler. See also PYTHONPERFSUPPORT=1.
  • -X perf_jit โ€” support the Linux "perf" profiler with DWARF support. See also PYTHON_PERF_JIT_SUPPORT=1.
  • -X presite=MOD โ€” import this module before site. See also PYTHON_PRESITE. This only works on debug builds.
  • -X pycache_prefix=PATH โ€” enable writing .pyc files to a parallel tree rooted at the given directory instead of to the code tree.
  • -X showrefcount โ€” output the total reference count and number of used memory blocks when the program finishes or after each statement in the interactive interpreter. This only works on debug builds.
  • -X tracemalloc โ€” start tracing Python memory allocations using the tracemalloc module. By default, only the most recent frame is stored in a traceback of a trace. Use -X tracemalloc=NFRAME to start tracing with a traceback limit of NFRAME frames.
  • -X utf8 โ€” enable UTF-8 mode for operating system interfaces, overriding the default locale-aware mode. -X utf8=0 explicitly disables UTF-8 mode (even when it would otherwise activate automatically). See PYTHONUTF8 for more details.
  • -X warn_default_encoding โ€” enable opt-in EncodingWarning for 'encoding=None'.
  • -x โ€” skip the first line of the source. This is intended for a DOS specific hack only.
โš ๏ธ Warning bestie: with -x, the line numbers in error messages will be off by one! ๐Ÿ˜ญ Keep that in mind before you go blaming the wrong line.

๐ŸŒธ INTERPRETER INTERFACE ๐ŸŒธ

okay so bestie, the way the interpreter talks to you is literally giving UNIX shell energy, no cap. Here's the tea ๐Ÿต:

  • when you call it with standard input connected to a tty device, it prompts you for commands and executes them until it reads an EOF ๐Ÿซถ
  • when you call it with a file name argument, or with a file as standard input, it reads and executes a script from that file
  • when you call it with -c command, it executes the Python statement(s) given as command. and command can absolutely contain multiple statements separated by newlines ๐Ÿ’…
โš ๏ธ Leading whitespace is significant in Python statements! do not be out here deleting your indentation bestie, it WILL humble you ๐Ÿ˜ญ

also: in non-interactive mode, the entire input is parsed before it is executed. like, all of it, first, then it runs. that's just how it is ๐Ÿ’–


if available, the script name and any additional arguments after it get passed to your script in the Python variable sys.argv, which is a list of strings (and yes you must first import sys to be able to access it, bestie, it's not just vibing in your namespace for free ๐Ÿ™ˆ).

  • if no script name is given, sys.argv[0] is an empty string
  • if -c is used, sys.argv[0] contains the string '-c'

and heads up: options interpreted by the Python interpreter itself are not placed in sys.argv. they're not invited to that party โœจ


in interactive mode, the primary prompt is >>>' and the second prompt (the one that shows up when a command is not complete) is ...'. you can change these prompts by assignment to sys.ps1 or sys.ps2 โ€” main character customization, honestly ๐Ÿ‘‘

the interpreter quits when it reads an EOF at a prompt. when an unhandled exception occurs, a stack trace is printed and control returns to the primary prompt ๐ŸŒˆ. but in non-interactive mode, the interpreter exits after printing the stack trace. different vibes entirely.

the interrupt signal raises the KeyboardInterrupt exception ๐Ÿ’€. other UNIX signals are not caught โ€” except that SIGPIPE is sometimes ignored, in favor of the IOError exception.

error messages are written to stderr. that's just where they live ๐ŸŽ€


๐ŸŽ€ FILES AND DIRECTORIES ๐ŸŽ€

these are subject to difference depending on local installation conventions, so don't come for them if yours look different, bestie. ${prefix} and ${exec_prefix} are installation-dependent and should be interpreted as for GNU software; they may be the same ๐Ÿ’œ. the default for both is /usr/local.

  • ${exec_prefix}/bin/python โ€” recommended location of the interpreter. that's the one, the icon, the moment โญ
  • ${prefix}/lib/python<version>
  • ${exec_prefix}/lib/python<version>

recommended locations of the directories containing the standard modules ๐Ÿ“ฆ

  • ${prefix}/include/python<version>
  • ${exec_prefix}/include/python<version>

recommended locations of the directories containing the include files needed for developing Python extensions and embedding the interpreter ๐Ÿงš


โœจ ENVIRONMENT VARIABLES โœจ

okay this is the big one, the whole mood board of env vars. every single one, in order, no skipping ๐Ÿ’…

  • PYTHONASYNCIODEBUG โ€” if this environment variable is set to a non-empty string, enable the debug mode of the asyncio module ๐Ÿฆ‹
  • PYTHON_BASIC_REPL โ€” if this variable is set to any value, the interpreter will not attempt to load the Python-based REPL that requires curses and readline, and will instead use the traditional parser-based REPL. retro vibes only ๐Ÿ”ฅ
  • PYTHONBREAKPOINT โ€” if this environment variable is set to 0, it disables the default debugger. it can be set to the callable of your debugger of choice ๐Ÿ‘‘
  • PYTHONCOERCECLOCALE โ€” if set to the value 0, causes the main Python command line application to skip coercing the legacy ASCII-based C and POSIX locales to a more capable UTF-8 based alternative ๐ŸŒˆ
  • PYTHON_COLORS โ€” if this variable is set to 1, the interpreter will colorize various kinds of output. setting it to 0 deactivates this behavior. color is a lifestyle ๐Ÿ’–
  • PYTHON_CPU_COUNT โ€” if this variable is set to a positive integer, it overrides the return values of os.cpu_count and os.process_cpu_count.

see also the -X cpu_count option.

  • PYTHONDEBUG โ€” if this is set to a non-empty string it is equivalent to specifying the -d option. if set to an integer, it is equivalent to specifying -d multiple times ๐Ÿ”
  • PYTHONEXECUTABLE โ€” if this environment variable is set, sys.argv[0] will be set to its value instead of the value got through the C runtime. Only works on Mac OS X. ๐Ÿ“
  • PYTHONFAULTHANDLER โ€” if this environment variable is set to a non-empty string, faulthandler.enable() is called at startup: install a handler for SIGSEGV, SIGFPE, SIGABRT, SIGBUS and SIGILL signals to dump the Python traceback ๐Ÿ’€

this is equivalent to the -X faulthandler option.

  • PYTHON_FROZEN_MODULES โ€” if this variable is set to on or off, it determines whether or not frozen modules are ignored by the import machinery. a value of on means they get imported and off means they are ignored. the default is on for non-debug builds (the normal case) and off for debug builds.

see also the -X frozen_modules option.

  • PYTHON_GIL โ€” if this variable is set to 1, the global interpreter lock (GIL) will be forced on. setting it to 0 forces the GIL off. only available in builds configured with --disable-gil. โš ๏ธ niche but iconic

this is equivalent to the -X gil option.

  • PYTHON_HISTORY โ€” this environment variable can be used to set the location of a history file (on Unix, it is ~/.python_history by default) ๐Ÿ“œ
  • PYTHONNODEBUGRANGES โ€” if this variable is set, it disables the inclusion of the tables mapping extra location information (end line, start column offset and end column offset) to every instruction in code objects. this is useful when smaller code objects and pyc files are desired, as well as suppressing the extra visual location indicators when the interpreter displays tracebacks โœจ
  • PYTHONDONTWRITEBYTECODE โ€” if this is set to a non-empty string it is equivalent to specifying the -B option (don't try to write .pyc files) ๐Ÿ™ˆ
  • PYTHONDEVMODE โ€” if this environment variable is set to a non-empty string, enable Python's "development mode", introducing additional runtime checks that are too expensive to be enabled by default ๐Ÿ’…

this is equivalent to the -X dev option.

  • PYTHONHASHSEED โ€” if this variable is set to "random", a random value is used to seed the hashes of str and bytes objects.

if PYTHONHASHSEED is set to an integer value, it is used as a fixed seed for generating the hash() of the types covered by the hash randomization. its purpose is to allow repeatable hashing, such as for selftests for the interpreter itself, or to allow a cluster of python processes to share hash values.

the integer must be a decimal number in the range [0,4294967295]. specifying the value 0 will disable hash randomization.

  • PYTHONHOME โ€” change the location of the standard Python libraries. by default, the libraries are searched in ${prefix}/lib/python<version> and ${exec_prefix}/lib/python<version>, where ${prefix} and ${exec_prefix} are installation-dependent directories, both defaulting to /usr/local. when $PYTHONHOME is set to a single directory, its value replaces both ${prefix} and ${exec_prefix}. to specify different values for these, set $PYTHONHOME to ${prefix}:${exec_prefix} ๐Ÿ 
  • PYTHONINSPECT โ€” if this is set to a non-empty string it is equivalent to specifying the -i option ๐Ÿ‘€
  • PYTHONINTMAXSTRDIGITS โ€” limit the maximum digit characters in an int value when converting from a string and when converting an int back to a str. a value of 0 disables the limit. conversions to or from bases 2, 4, 8, 16, and 32 are never limited ๐Ÿ”ข

this is equivalent to the -X int_max_str_digits=NUMBER option.

  • PYTHONIOENCODING โ€” if this is set before running the interpreter, it overrides the encoding used for stdin/stdout/stderr, in the syntax encodingname:errorhandler. the errorhandler part is optional and has the same meaning as in str.encode. for stderr, the errorhandler part is ignored; the handler will always be backslashreplace ๐Ÿ’œ
  • PYTHONMALLOC โ€” set the Python memory allocators and/or install debug hooks. the available memory allocators are malloc and pymalloc. the available debug hooks are debug, malloc_debug, and pymalloc_debug.

when Python is compiled in debug mode, the default is pymalloc_debug and the debug hooks are automatically used. otherwise, the default is pymalloc ๐Ÿง 

  • PYTHONMALLOCSTATS โ€” if set to a non-empty string, Python will print statistics of the pymalloc memory allocator every time a new pymalloc object arena is created, and on shutdown ๐Ÿ“Š

this variable is ignored if the $PYTHONMALLOC environment variable is used to force the malloc(3) allocator of the C library, or if Python is configured without pymalloc support.

  • PYTHONNOUSERSITE โ€” if this is set to a non-empty string it is equivalent to specifying the -s option (Don't add the user site directory to sys.path) ๐Ÿ™…โ™€๏ธ
  • PYTHONOPTIMIZE โ€” if this is set to a non-empty string it is equivalent to specifying the -O option. if set to an integer, it is equivalent to specifying -O multiple times โšก
  • PYTHONPATH โ€” augments the default search path for module files. the format is the same as the shell's $PATH: one or more directory pathnames separated by colons. non-existent directories are silently ignored. the default search path is installation dependent, but generally begins with ${prefix}/lib/python<version> (see PYTHONHOME above). the default search path is always appended to $PYTHONPATH. if a script argument is given, the directory containing the script is inserted in the path in front of $PYTHONPATH. the search path can be manipulated from within a Python program as the variable sys.path ๐Ÿ›ฃ๏ธ
  • PYTHON_PERF_JIT_SUPPORT โ€” if this variable is set to a nonzero value, it enables support for the Linux perf profiler so Python calls can be detected by it using DWARF information. setting to 0 disables ๐Ÿ”ฅ

see also the -X perf_jit option.

  • PYTHONPERFSUPPORT โ€” if this variable is set to a nonzero value, it enables support for the Linux perf profiler so Python calls can be detected by it. setting to 0 disables ๐Ÿ”ฅ

see also the -X perf option.

  • PYTHONPLATLIBDIR โ€” override sys.platlibdir. short, sweet, iconic ๐Ÿ’…
  • PYTHONPROFILEIMPORTTIME โ€” if this environment variable is set to 1, Python will show how long each import takes. if set to 2, Python will include output for imported modules that have already been loaded. this is exactly equivalent to setting -X importtime on the command line โฑ๏ธ

okay bestie we're so back ๐Ÿ’…</p> the env var list is still going, and honestly? it ate. keep scrolling, we're almost at the finish line ๐Ÿ

  • PYTHONPYCACHEPREFIX โ€” set this and Python stops scattering .pyc files into __pycache__ folders all over your source tree (so messy of it). Instead it writes them into a mirror directory tree at the path you give it. Same energy as passing -X pycache_prefix=PATH. ๐Ÿ—‚๏ธ
  • PYTHONSAFEPATH โ€” if you set this to a non-empty string, Python will not automatically prepend a potentially unsafe path to sys.path โ€” think the current directory, the script's directory, or an empty string. Basically: don't let sketchy paths sneak into your import search. See also the -P option. ๐Ÿ›ก๏ธ
  • PYTHONSTARTUP โ€” if this points at the name of a readable file, the Python commands in that file get run before the first prompt shows up in interactive mode. And here's the cute part: it runs in the exact same namespace where your interactive commands run, so anything you define or import in there is just... available. No qualification needed. You can also use it to change the prompts sys.ps1 and sys.ps2. Main character setup fr. โœจ
  • PYTHONTRACEMALLOC โ€” non-empty string? Then Python starts tracing memory allocations using the tracemalloc module. The value itself is the maximum number of frames stored in a traceback of a trace. So like, PYTHONTRACEMALLOC=1 keeps only the most recent frame. Small number, small stack pic. ๐Ÿ“ธ
  • PYTHONUNBUFFERED โ€” set it to a non-empty string and it's the same as passing -u. That's it, that's the whole vibe. ๐ŸŒŠ
  • PYTHONUSERBASE โ€” defines the user base directory. Python uses it to figure out the path of the user site-packages directory, plus the installation paths for python -m pip install --user. ๐Ÿ 
  • PYTHONUTF8 โ€” set it to 1 and you turn on Python's "UTF-8 Mode". Set it to 0 and you turn it back off. On/off, that simple. ๐Ÿ”ค
  • PYTHONVERBOSE โ€” non-empty string โ†’ same as -v. But if you set it to an integer, it's like passing -v that many times. So PYTHONVERBOSE=3 is -v -v -v. Chatty icon. ๐Ÿ—ฃ๏ธ
  • PYTHONWARNDEFAULTENCODING โ€” non-empty string โ†’ Python raises an EncodingWarning whenever the locale-specific default encoding gets used. A lil heads up before things get weird. โš ๏ธ
  • PYTHONWARNINGS โ€” a comma-separated string โ†’ same as passing -W once for each separate value in the list. ๐Ÿšจ

๐Ÿ› Debug-mode variables ๐Ÿ›

important bestie: setting these only does anything in a debug build of Python โ€” meaning Python was configured with the --with-pydebug build option. Regular build? They're just sitting there, unbothered, doing nothing. ๐Ÿ’€
  • PYTHONDUMPREFS โ€” set it and Python dumps all the objects and reference counts that are still alive after the interpreter shuts down. Spilling the tea on leaked refs. ๐Ÿซ–
  • PYTHONDUMPREFSFILE โ€” same idea, but it dumps those still-alive objects and reference counts into a file located under the path you give as the value of this variable. Now the tea's in writing. ๐Ÿ“
  • PYTHON_PRESITE โ€” set this to a module and that module gets imported early in the interpreter lifecycle: before the site module executes, and before the __main__ module is even created. Only works on debug builds, as established. โœจ

This one is equivalent to the -X presite=module option. ๐Ÿช„


๐Ÿ‘‘ AUTHOR ๐Ÿ‘‘

The Python Software Foundation: https://www.python.org/psf/


๐ŸŒˆ INTERNET RESOURCES ๐ŸŒˆ


๐Ÿ“œ LICENSING ๐Ÿ“œ

Python is distributed under an Open Source license. Wanna know the terms & conditions for accessing and otherwise using Python, plus a DISCLAIMER OF ALL WARRANTIES? Check the file "LICENSE" in the Python source distribution. Go read it, bestie, it's giving responsible. ๐Ÿซถ


and that's the whole PYTHON(1) page, bestie ๐Ÿ’– the little footer at the bottom just said PYTHON(1) (y'know, the section 1 man page, which is where all the user commands live) โ€” so if you ever see that tag floating at the end of your man python, that's this page, telling you it's from the Python manual. Now go write something iconic with it. periodt. ๐Ÿ’…๐ŸŽ€๐Ÿฆ‹