neulab/docprompting-conala huggingface dataset:
sys.exit([arg])  
Exit from Python. This is implemented by raising the SystemExit exception, so cleanup actions specified by finally clauses of try statements are honored, and it is possible to intercept the exit attempt at an outer level. The optional argument arg can be an integer giving the exit status (defaulting to zero), or another type of object. If it is an integer, zero is considered “successful termination” and any nonzero value is considered “abnormal termination” by shells and the like. Most systems require it to be in the range 0–127, and produce undefined results otherwise. Some systems have a convention for assigning specific meanings to specific exit codes, but these are generally underdeveloped; Unix programs generally use 2 for command line syntax errors and 1 for all other kind of errors. If another type of object is passed, None is equivalent to passing zero, and any other object is printed to stderr and results in an exit code of 1. In particular, sys.exit("some error message") is a quick way to exit a program when an error occurs. Since exit() ultimately “only” raises an exception, it will only exit the process when called from the main thread, and the exception is not intercepted.  Changed in version 3.6: If an error occurs in the cleanup after the Python interpreter has caught SystemExit (such as an error flushing buffered data in the standard streams), the exit status is changed to 120.
sys.flags  
The named tuple flags exposes the status of command line flags. The attributes are read only.   
attribute flag   
debug -d  
inspect -i  
interactive -i  
isolated -I  
optimize -O or -OO  
dont_write_bytecode -B  
no_user_site -s  
no_site -S  
ignore_environment -E  
verbose -v  
bytes_warning -b  
quiet -q  
hash_randomization -R  
dev_mode -X dev (Python Development Mode)  
utf8_mode -X utf8    Changed in version 3.2: Added quiet attribute for the new -q flag.   New in version 3.2.3: The hash_randomization attribute.   Changed in version 3.3: Removed obsolete division_warning attribute.   Changed in version 3.4: Added isolated attribute for -I isolated flag.   Changed in version 3.7: Added the dev_mode attribute for the new Python Development Mode and the utf8_mode attribute for the new -X utf8 flag.
sys.float_info  
A named tuple holding information about the float type. It contains low level information about the precision and internal representation. The values correspond to the various floating-point constants defined in the standard header file float.h for the ‘C’ programming language; see section 5.2.4.2.2 of the 1999 ISO/IEC C standard [C99], ‘Characteristics of floating types’, for details.   
attribute float.h macro explanation   
epsilon DBL_EPSILON 
difference between 1.0 and the least value greater than 1.0 that is representable as a float See also math.ulp().   
dig DBL_DIG maximum number of decimal digits that can be faithfully represented in a float; see below  
mant_dig DBL_MANT_DIG float precision: the number of base-radix digits in the significand of a float  
max DBL_MAX maximum representable positive finite float  
max_exp DBL_MAX_EXP maximum integer e such that radix**(e-1) is a representable finite float  
max_10_exp DBL_MAX_10_EXP maximum integer e such that 10**e is in the range of representable finite floats  
min DBL_MIN 
minimum representable positive normalized float Use math.ulp(0.0) to get the smallest positive denormalized representable float.   
min_exp DBL_MIN_EXP minimum integer e such that radix**(e-1) is a normalized float  
min_10_exp DBL_MIN_10_EXP minimum integer e such that 10**e is a normalized float  
radix FLT_RADIX radix of exponent representation  
rounds FLT_ROUNDS integer constant representing the rounding mode used for arithmetic operations. This reflects the value of the system FLT_ROUNDS macro at interpreter startup time. See section 5.2.4.2.2 of the C99 standard for an explanation of the possible values and their meanings.   The attribute sys.float_info.dig needs further explanation. If s is any string representing a decimal number with at most sys.float_info.dig significant digits, then converting s to a float and back again will recover a string representing the same decimal value: >>> import sys
>>> sys.float_info.dig
15
>>> s = '3.14159265358979'    # decimal string with 15 significant digits
>>> format(float(s), '.15g')  # convert to float and back -> same value
'3.14159265358979'
 But for strings with more than sys.float_info.dig significant digits, this isn’t always true: >>> s = '9876543211234567'    # 16 significant digits is too many!
>>> format(float(s), '.16g')  # conversion changes value
'9876543211234568'
sys.float_repr_style  
A string indicating how the repr() function behaves for floats. If the string has value 'short' then for a finite float x, repr(x) aims to produce a short string with the property that float(repr(x)) == x. This is the usual behaviour in Python 3.1 and later. Otherwise, float_repr_style has value 'legacy' and repr(x) behaves in the same way as it did in versions of Python prior to 3.1.  New in version 3.1.
sys.getallocatedblocks()  
Return the number of memory blocks currently allocated by the interpreter, regardless of their size. This function is mainly useful for tracking and debugging memory leaks. Because of the interpreter’s internal caches, the result can vary from call to call; you may have to call _clear_type_cache() and gc.collect() to get more predictable results. If a Python build or implementation cannot reasonably compute this information, getallocatedblocks() is allowed to return 0 instead.  New in version 3.4.
sys.getandroidapilevel()  
Return the build time API version of Android as an integer. Availability: Android.  New in version 3.7.
sys.getdefaultencoding()  
Return the name of the current default string encoding used by the Unicode implementation.
sys.getdlopenflags()  
Return the current value of the flags that are used for dlopen() calls. Symbolic names for the flag values can be found in the os module (RTLD_xxx constants, e.g. os.RTLD_LAZY). Availability: Unix.
sys.getfilesystemencodeerrors()  
Return the name of the error mode used to convert between Unicode filenames and bytes filenames. The encoding name is returned from getfilesystemencoding(). os.fsencode() and os.fsdecode() should be used to ensure that the correct encoding and errors mode are used.  New in version 3.6.
sys.getfilesystemencoding()  
Return the name of the encoding used to convert between Unicode filenames and bytes filenames. For best compatibility, str should be used for filenames in all cases, although representing filenames as bytes is also supported. Functions accepting or returning filenames should support either str or bytes and internally convert to the system’s preferred representation. This encoding is always ASCII-compatible. os.fsencode() and os.fsdecode() should be used to ensure that the correct encoding and errors mode are used.  In the UTF-8 mode, the encoding is utf-8 on any platform. On macOS, the encoding is 'utf-8'. On Unix, the encoding is the locale encoding. On Windows, the encoding may be 'utf-8' or 'mbcs', depending on user configuration. On Android, the encoding is 'utf-8'. On VxWorks, the encoding is 'utf-8'.   Changed in version 3.2: getfilesystemencoding() result cannot be None anymore.   Changed in version 3.6: Windows is no longer guaranteed to return 'mbcs'. See PEP 529 and _enablelegacywindowsfsencoding() for more information.   Changed in version 3.7: Return ‘utf-8’ in the UTF-8 mode.
sys.getrecursionlimit()  
Return the current value of the recursion limit, the maximum depth of the Python interpreter stack. This limit prevents infinite recursion from causing an overflow of the C stack and crashing Python. It can be set by setrecursionlimit().
sys.getrefcount(object)  
Return the reference count of the object. The count returned is generally one higher than you might expect, because it includes the (temporary) reference as an argument to getrefcount().
sys.getsizeof(object[, default])  
Return the size of an object in bytes. The object can be any type of object. All built-in objects will return correct results, but this does not have to hold true for third-party extensions as it is implementation specific. Only the memory consumption directly attributed to the object is accounted for, not the memory consumption of objects it refers to. If given, default will be returned if the object does not provide means to retrieve the size. Otherwise a TypeError will be raised. getsizeof() calls the object’s __sizeof__ method and adds an additional garbage collector overhead if the object is managed by the garbage collector. See recursive sizeof recipe for an example of using getsizeof() recursively to find the size of containers and all their contents.
sys.getswitchinterval()  
Return the interpreter’s “thread switch interval”; see setswitchinterval().  New in version 3.2.
sys.gettrace()  
Get the trace function as set by settrace().  CPython implementation detail: The gettrace() function is intended only for implementing debuggers, profilers, coverage tools and the like. Its behavior is part of the implementation platform, rather than part of the language definition, and thus may not be available in all Python implementations.
sys.getwindowsversion()  
Return a named tuple describing the Windows version currently running. The named elements are major, minor, build, platform, service_pack, service_pack_minor, service_pack_major, suite_mask, product_type and platform_version. service_pack contains a string, platform_version a 3-tuple and all other values are integers. The components can also be accessed by name, so sys.getwindowsversion()[0] is equivalent to sys.getwindowsversion().major. For compatibility with prior versions, only the first 5 elements are retrievable by indexing. platform will be 2 (VER_PLATFORM_WIN32_NT). product_type may be one of the following values:   
Constant Meaning   
1 (VER_NT_WORKSTATION) The system is a workstation.  
2 (VER_NT_DOMAIN_CONTROLLER) The system is a domain controller.  
3 (VER_NT_SERVER) The system is a server, but not a domain controller.   This function wraps the Win32 GetVersionEx() function; see the Microsoft documentation on OSVERSIONINFOEX() for more information about these fields. platform_version returns the major version, minor version and build number of the current operating system, rather than the version that is being emulated for the process. It is intended for use in logging rather than for feature detection.  Note platform_version derives the version from kernel32.dll which can be of a different version than the OS version. Please use platform module for achieving accurate OS version.  Availability: Windows.  Changed in version 3.2: Changed to a named tuple and added service_pack_minor, service_pack_major, suite_mask, and product_type.   Changed in version 3.6: Added platform_version
sys.get_asyncgen_hooks()  
Returns an asyncgen_hooks object, which is similar to a namedtuple of the form (firstiter, finalizer), where firstiter and finalizer are expected to be either None or functions which take an asynchronous generator iterator as an argument, and are used to schedule finalization of an asynchronous generator by an event loop.  New in version 3.6: See PEP 525 for more details.   Note This function has been added on a provisional basis (see PEP 411 for details.)
sys.get_coroutine_origin_tracking_depth()  
Get the current coroutine origin tracking depth, as set by set_coroutine_origin_tracking_depth().  New in version 3.7.   Note This function has been added on a provisional basis (see PEP 411 for details.) Use it only for debugging purposes.
sys.hash_info  
A named tuple giving parameters of the numeric hash implementation. For more details about hashing of numeric types, see Hashing of numeric types.   
attribute explanation   
width width in bits used for hash values  
modulus prime modulus P used for numeric hash scheme  
inf hash value returned for a positive infinity  
nan hash value returned for a nan  
imag multiplier used for the imaginary part of a complex number  
algorithm name of the algorithm for hashing of str, bytes, and memoryview  
hash_bits internal output size of the hash algorithm  
seed_bits size of the seed key of the hash algorithm    New in version 3.2.   Changed in version 3.4: Added algorithm, hash_bits and seed_bits
sys.hexversion  
The version number encoded as a single integer. This is guaranteed to increase with each version, including proper support for non-production releases. For example, to test that the Python interpreter is at least version 1.5.2, use: if sys.hexversion >= 0x010502F0:
    # use some advanced feature
    ...
else:
    # use an alternative implementation or warn the user
    ...
 This is called hexversion since it only really looks meaningful when viewed as the result of passing it to the built-in hex() function. The named tuple sys.version_info may be used for a more human-friendly encoding of the same information. More details of hexversion can be found at API and ABI Versioning.
sys.implementation  
An object containing information about the implementation of the currently running Python interpreter. The following attributes are required to exist in all Python implementations. name is the implementation’s identifier, e.g. 'cpython'. The actual string is defined by the Python implementation, but it is guaranteed to be lower case. version is a named tuple, in the same format as sys.version_info. It represents the version of the Python implementation. This has a distinct meaning from the specific version of the Python language to which the currently running interpreter conforms, which sys.version_info represents. For example, for PyPy 1.8 sys.implementation.version might be sys.version_info(1, 8, 0, 'final', 0), whereas sys.version_info would be sys.version_info(2, 7, 2, 'final', 0). For CPython they are the same value, since it is the reference implementation. hexversion is the implementation version in hexadecimal format, like sys.hexversion. cache_tag is the tag used by the import machinery in the filenames of cached modules. By convention, it would be a composite of the implementation’s name and version, like 'cpython-33'. However, a Python implementation may use some other value if appropriate. If cache_tag is set to None, it indicates that module caching should be disabled. sys.implementation may contain additional attributes specific to the Python implementation. These non-standard attributes must start with an underscore, and are not described here. Regardless of its contents, sys.implementation will not change during a run of the interpreter, nor between implementation versions. (It may change between Python language versions, however.) See PEP 421 for more information.  New in version 3.3.   Note The addition of new required attributes must go through the normal PEP process. See PEP 421 for more information.
sys.intern(string)  
Enter string in the table of “interned” strings and return the interned string – which is string itself or a copy. Interning strings is useful to gain a little performance on dictionary lookup – if the keys in a dictionary are interned, and the lookup key is interned, the key comparisons (after hashing) can be done by a pointer compare instead of a string compare. Normally, the names used in Python programs are automatically interned, and the dictionaries used to hold module, class or instance attributes have interned keys. Interned strings are not immortal; you must keep a reference to the return value of intern() around to benefit from it.
sys.int_info  
A named tuple that holds information about Python’s internal representation of integers. The attributes are read only.   
Attribute Explanation   
bits_per_digit number of bits held in each digit. Python integers are stored internally in base 2**int_info.bits_per_digit  
sizeof_digit size in bytes of the C type used to represent a digit    New in version 3.1.
sys.is_finalizing()  
Return True if the Python interpreter is shutting down, False otherwise.  New in version 3.5.
sys.last_type  
sys.last_value  
sys.last_traceback  
These three variables are not always defined; they are set when an exception is not handled and the interpreter prints an error message and a stack traceback. Their intended use is to allow an interactive user to import a debugger module and engage in post-mortem debugging without having to re-execute the command that caused the error. (Typical use is import pdb; pdb.pm() to enter the post-mortem debugger; see pdb module for more information.) The meaning of the variables is the same as that of the return values from exc_info() above.
sys.maxsize  
An integer giving the maximum value a variable of type Py_ssize_t can take. It’s usually 2**31 - 1 on a 32-bit platform and 2**63 - 1 on a 64-bit platform.
sys.maxunicode  
An integer giving the value of the largest Unicode code point, i.e. 1114111 (0x10FFFF in hexadecimal).  Changed in version 3.3: Before PEP 393, sys.maxunicode used to be either 0xFFFF or 0x10FFFF, depending on the configuration option that specified whether Unicode characters were stored as UCS-2 or UCS-4.
sys.meta_path  
A list of meta path finder objects that have their find_spec() methods called to see if one of the objects can find the module to be imported. The find_spec() method is called with at least the absolute name of the module being imported. If the module to be imported is contained in a package, then the parent package’s __path__ attribute is passed in as a second argument. The method returns a module spec, or None if the module cannot be found.  See also  
importlib.abc.MetaPathFinder


The abstract base class defining the interface of finder objects on meta_path.  
importlib.machinery.ModuleSpec


The concrete class which find_spec() should return instances of.     Changed in version 3.4: Module specs were introduced in Python 3.4, by PEP 451. Earlier versions of Python looked for a method called find_module(). This is still called as a fallback if a meta_path entry doesn’t have a find_spec() method.
sys.modules  
This is a dictionary that maps module names to modules which have already been loaded. This can be manipulated to force reloading of modules and other tricks. However, replacing the dictionary will not necessarily work as expected and deleting essential items from the dictionary may cause Python to fail.
sys.path  
A list of strings that specifies the search path for modules. Initialized from the environment variable PYTHONPATH, plus an installation-dependent default. As initialized upon program startup, the first item of this list, path[0], is the directory containing the script that was used to invoke the Python interpreter. If the script directory is not available (e.g. if the interpreter is invoked interactively or if the script is read from standard input), path[0] is the empty string, which directs Python to search modules in the current directory first. Notice that the script directory is inserted before the entries inserted as a result of PYTHONPATH. A program is free to modify this list for its own purposes. Only strings and bytes should be added to sys.path; all other data types are ignored during import.  See also Module site This describes how to use .pth files to extend sys.path.
sys.path_hooks  
A list of callables that take a path argument to try to create a finder for the path. If a finder can be created, it is to be returned by the callable, else raise ImportError. Originally specified in PEP 302.
sys.path_importer_cache  
A dictionary acting as a cache for finder objects. The keys are paths that have been passed to sys.path_hooks and the values are the finders that are found. If a path is a valid file system path but no finder is found on sys.path_hooks then None is stored. Originally specified in PEP 302.  Changed in version 3.3: None is stored instead of imp.NullImporter when no finder is found.
sys.platform  
This string contains a platform identifier that can be used to append platform-specific components to sys.path, for instance. For Unix systems, except on Linux and AIX, this is the lowercased OS name as returned by uname -s with the first part of the version as returned by uname -r appended, e.g. 'sunos5' or 'freebsd8', at the time when Python was built. Unless you want to test for a specific system version, it is therefore recommended to use the following idiom: if sys.platform.startswith('freebsd'):
    # FreeBSD-specific code here...
elif sys.platform.startswith('linux'):
    # Linux-specific code here...
elif sys.platform.startswith('aix'):
    # AIX-specific code here...
 For other systems, the values are:   
System platform value   
AIX 'aix'  
Linux 'linux'  
Windows 'win32'  
Windows/Cygwin 'cygwin'  
macOS 'darwin'    Changed in version 3.3: On Linux, sys.platform doesn’t contain the major version anymore. It is always 'linux', instead of 'linux2' or 'linux3'. Since older Python versions include the version number, it is recommended to always use the startswith idiom presented above.   Changed in version 3.8: On AIX, sys.platform doesn’t contain the major version anymore. It is always 'aix', instead of 'aix5' or 'aix7'. Since older Python versions include the version number, it is recommended to always use the startswith idiom presented above.   See also os.name has a coarser granularity. os.uname() gives system-dependent version information. The platform module provides detailed checks for the system’s identity.
sys.platlibdir  
Name of the platform-specific library directory. It is used to build the path of standard library and the paths of installed extension modules. It is equal to "lib" on most platforms. On Fedora and SuSE, it is equal to "lib64" on 64-bit platforms which gives the following sys.path paths (where X.Y is the Python major.minor version):  
/usr/lib64/pythonX.Y/: Standard library (like os.py of the os module) 
/usr/lib64/pythonX.Y/lib-dynload/: C extension modules of the standard library (like the errno module, the exact filename is platform specific) 
/usr/lib/pythonX.Y/site-packages/ (always use lib, not sys.platlibdir): Third-party modules 
/usr/lib64/pythonX.Y/site-packages/: C extension modules of third-party packages   New in version 3.9.
sys.prefix  
A string giving the site-specific directory prefix where the platform independent Python files are installed; by default, this is the string '/usr/local'. This can be set at build time with the --prefix argument to the configure script. The main collection of Python library modules is installed in the directory prefix/lib/pythonX.Y while the platform independent header files (all except pyconfig.h) are stored in prefix/include/pythonX.Y, where X.Y is the version number of Python, for example 3.2.  Note If a virtual environment is in effect, this value will be changed in site.py to point to the virtual environment. The value for the Python installation will still be available, via base_prefix.
sys.ps1  
sys.ps2  
Strings specifying the primary and secondary prompt of the interpreter. These are only defined if the interpreter is in interactive mode. Their initial values in this case are '>>> ' and '... '. If a non-string object is assigned to either variable, its str() is re-evaluated each time the interpreter prepares to read a new interactive command; this can be used to implement a dynamic prompt.
sys.pycache_prefix  
If this is set (not None), Python will write bytecode-cache .pyc files to (and read them from) a parallel directory tree rooted at this directory, rather than from __pycache__ directories in the source code tree. Any __pycache__ directories in the source code tree will be ignored and new .pyc files written within the pycache prefix. Thus if you use compileall as a pre-build step, you must ensure you run it with the same pycache prefix (if any) that you will use at runtime. A relative path is interpreted relative to the current working directory. This value is initially set based on the value of the -X pycache_prefix=PATH command-line option or the PYTHONPYCACHEPREFIX environment variable (command-line takes precedence). If neither are set, it is None.  New in version 3.8.