Built-in Exceptions¶
In Python, all exceptions must be instances of a class that derives from BaseException . In a try statement with an except clause that mentions a particular class, that clause also handles any exception classes derived from that class (but not exception classes from which it is derived). Two exception classes that are not related via subclassing are never equivalent, even if they have the same name.
The built-in exceptions listed below can be generated by the interpreter or built-in functions. Except where mentioned, they have an “associated value” indicating the detailed cause of the error. This may be a string or a tuple of several items of information (e.g., an error code and a string explaining the code). The associated value is usually passed as arguments to the exception class’s constructor.
User code can raise built-in exceptions. This can be used to test an exception handler or to report an error condition “just like” the situation in which the interpreter raises the same exception; but beware that there is nothing to prevent user code from raising an inappropriate error.
The built-in exception classes can be subclassed to define new exceptions; programmers are encouraged to derive new exceptions from the Exception class or one of its subclasses, and not from BaseException . More information on defining exceptions is available in the Python Tutorial under User-defined Exceptions .
Exception context¶
When raising a new exception while another exception is already being handled, the new exception’s __context__ attribute is automatically set to the handled exception. An exception may be handled when an except or finally clause, or a with statement, is used.
This implicit exception context can be supplemented with an explicit cause by using from with raise :
The expression following from must be an exception or None . It will be set as __cause__ on the raised exception. Setting __cause__ also implicitly sets the __suppress_context__ attribute to True , so that using raise new_exc from None effectively replaces the old exception with the new one for display purposes (e.g. converting KeyError to AttributeError ), while leaving the old exception available in __context__ for introspection when debugging.
The default traceback display code shows these chained exceptions in addition to the traceback for the exception itself. An explicitly chained exception in __cause__ is always shown when present. An implicitly chained exception in __context__ is shown only if __cause__ is None and __suppress_context__ is false.
In either case, the exception itself is always shown after any chained exceptions so that the final line of the traceback always shows the last exception that was raised.
Inheriting from built-in exceptions¶
User code can create subclasses that inherit from an exception type. It’s recommended to only subclass one exception type at a time to avoid any possible conflicts between how the bases handle the args attribute, as well as due to possible memory layout incompatibilities.
CPython implementation detail: Most built-in exceptions are implemented in C for efficiency, see: Objects/exceptions.c. Some have custom memory layouts which makes it impossible to create a subclass that inherits from multiple exception types. The memory layout of a type is an implementation detail and might change between Python versions, leading to new conflicts in the future. Therefore, it’s recommended to avoid subclassing multiple exception types altogether.
Base classes¶
The following exceptions are used mostly as base classes for other exceptions.
The base class for all built-in exceptions. It is not meant to be directly inherited by user-defined classes (for that, use Exception ). If str() is called on an instance of this class, the representation of the argument(s) to the instance are returned, or the empty string when there were no arguments.
The tuple of arguments given to the exception constructor. Some built-in exceptions (like OSError ) expect a certain number of arguments and assign a special meaning to the elements of this tuple, while others are usually called only with a single string giving an error message.
This method sets tb as the new traceback for the exception and returns the exception object. It was more commonly used before the exception chaining features of PEP 3134 became available. The following example shows how we can convert an instance of SomeException into an instance of OtherException while preserving the traceback. Once raised, the current frame is pushed onto the traceback of the OtherException , as would have happened to the traceback of the original SomeException had we allowed it to propagate to the caller.
Add the string note to the exception’s notes which appear in the standard traceback after the exception string. A TypeError is raised if note is not a string.
New in version 3.11.
A list of the notes of this exception, which were added with add_note() . This attribute is created when add_note() is called.
New in version 3.11.
All built-in, non-system-exiting exceptions are derived from this class. All user-defined exceptions should also be derived from this class.
The base class for those built-in exceptions that are raised for various arithmetic errors: OverflowError , ZeroDivisionError , FloatingPointError .
Raised when a buffer related operation cannot be performed.
The base class for the exceptions that are raised when a key or index used on a mapping or sequence is invalid: IndexError , KeyError . This can be raised directly by codecs.lookup() .
Concrete exceptions¶
The following exceptions are the exceptions that are usually raised.
Raised when an assert statement fails.
Raised when an attribute reference (see Attribute references ) or assignment fails. (When an object does not support attribute references or attribute assignments at all, TypeError is raised.)
The name and obj attributes can be set using keyword-only arguments to the constructor. When set they represent the name of the attribute that was attempted to be accessed and the object that was accessed for said attribute, respectively.
Changed in version 3.10: Added the name and obj attributes.
Raised when the input() function hits an end-of-file condition (EOF) without reading any data. (N.B.: the io.IOBase.read() and io.IOBase.readline() methods return an empty string when they hit EOF.)
Not currently used.
Raised when a generator or coroutine is closed; see generator.close() and coroutine.close() . It directly inherits from BaseException instead of Exception since it is technically not an error.
Raised when the import statement has troubles trying to load a module. Also raised when the “from list” in from . import has a name that cannot be found.
The name and path attributes can be set using keyword-only arguments to the constructor. When set they represent the name of the module that was attempted to be imported and the path to any file which triggered the exception, respectively.
Changed in version 3.3: Added the name and path attributes.
A subclass of ImportError which is raised by import when a module could not be located. It is also raised when None is found in sys.modules .
New in version 3.6.
Raised when a sequence subscript is out of range. (Slice indices are silently truncated to fall in the allowed range; if an index is not an integer, TypeError is raised.)
Raised when a mapping (dictionary) key is not found in the set of existing keys.
Raised when the user hits the interrupt key (normally Control — C or Delete ). During execution, a check for interrupts is made regularly. The exception inherits from BaseException so as to not be accidentally caught by code that catches Exception and thus prevent the interpreter from exiting.
Catching a KeyboardInterrupt requires special consideration. Because it can be raised at unpredictable points, it may, in some circumstances, leave the running program in an inconsistent state. It is generally best to allow KeyboardInterrupt to end the program as quickly as possible or avoid raising it entirely. (See Note on Signal Handlers and Exceptions .)
Raised when an operation runs out of memory but the situation may still be rescued (by deleting some objects). The associated value is a string indicating what kind of (internal) operation ran out of memory. Note that because of the underlying memory management architecture (C’s malloc() function), the interpreter may not always be able to completely recover from this situation; it nevertheless raises an exception so that a stack traceback can be printed, in case a run-away program was the cause.
Raised when a local or global name is not found. This applies only to unqualified names. The associated value is an error message that includes the name that could not be found.
The name attribute can be set using a keyword-only argument to the constructor. When set it represent the name of the variable that was attempted to be accessed.
Changed in version 3.10: Added the name attribute.
This exception is derived from RuntimeError . In user defined base classes, abstract methods should raise this exception when they require derived classes to override the method, or while the class is being developed to indicate that the real implementation still needs to be added.
It should not be used to indicate that an operator or method is not meant to be supported at all – in that case either leave the operator / method undefined or, if a subclass, set it to None .
NotImplementedError and NotImplemented are not interchangeable, even though they have similar names and purposes. See NotImplemented for details on when to use it.
This exception is raised when a system function returns a system-related error, including I/O failures such as “file not found” or “disk full” (not for illegal argument types or other incidental errors).
The second form of the constructor sets the corresponding attributes, described below. The attributes default to None if not specified. For backwards compatibility, if three arguments are passed, the args attribute contains only a 2-tuple of the first two constructor arguments.
The constructor often actually returns a subclass of OSError , as described in OS exceptions below. The particular subclass depends on the final errno value. This behaviour only occurs when constructing OSError directly or via an alias, and is not inherited when subclassing.
A numeric error code from the C variable errno .
Under Windows, this gives you the native Windows error code. The errno attribute is then an approximate translation, in POSIX terms, of that native error code.
Under Windows, if the winerror constructor argument is an integer, the errno attribute is determined from the Windows error code, and the errno argument is ignored. On other platforms, the winerror argument is ignored, and the winerror attribute does not exist.
The corresponding error message, as provided by the operating system. It is formatted by the C functions perror() under POSIX, and FormatMessage() under Windows.
For exceptions that involve a file system path (such as open() or os.unlink() ), filename is the file name passed to the function. For functions that involve two file system paths (such as os.rename() ), filename2 corresponds to the second file name passed to the function.
Changed in version 3.3: EnvironmentError , IOError , WindowsError , socket.error , select.error and mmap.error have been merged into OSError , and the constructor may return a subclass.
Changed in version 3.4: The filename attribute is now the original file name passed to the function, instead of the name encoded to or decoded from the filesystem encoding and error handler . Also, the filename2 constructor argument and attribute was added.
Raised when the result of an arithmetic operation is too large to be represented. This cannot occur for integers (which would rather raise MemoryError than give up). However, for historical reasons, OverflowError is sometimes raised for integers that are outside a required range. Because of the lack of standardization of floating point exception handling in C, most floating point operations are not checked.
This exception is derived from RuntimeError . It is raised when the interpreter detects that the maximum recursion depth (see sys.getrecursionlimit() ) is exceeded.
New in version 3.5: Previously, a plain RuntimeError was raised.
This exception is raised when a weak reference proxy, created by the weakref.proxy() function, is used to access an attribute of the referent after it has been garbage collected. For more information on weak references, see the weakref module.
Raised when an error is detected that doesn’t fall in any of the other categories. The associated value is a string indicating what precisely went wrong.
Raised by built-in function next() and an iterator ‘s __next__() method to signal that there are no further items produced by the iterator.
The exception object has a single attribute value , which is given as an argument when constructing the exception, and defaults to None .
When a generator or coroutine function returns, a new StopIteration instance is raised, and the value returned by the function is used as the value parameter to the constructor of the exception.
If a generator code directly or indirectly raises StopIteration , it is converted into a RuntimeError (retaining the StopIteration as the new exception’s cause).
Changed in version 3.3: Added value attribute and the ability for generator functions to use it to return a value.
Changed in version 3.5: Introduced the RuntimeError transformation via from __future__ import generator_stop , see PEP 479.
Changed in version 3.7: Enable PEP 479 for all code by default: a StopIteration error raised in a generator is transformed into a RuntimeError .
Must be raised by __anext__() method of an asynchronous iterator object to stop the iteration.
New in version 3.5.
Raised when the parser encounters a syntax error. This may occur in an import statement, in a call to the built-in functions compile() , exec() , or eval() , or when reading the initial script or standard input (also interactively).
The str() of the exception instance returns only the error message. Details is a tuple whose members are also available as separate attributes.
The name of the file the syntax error occurred in.
Which line number in the file the error occurred in. This is 1-indexed: the first line in the file has a lineno of 1.
The column in the line where the error occurred. This is 1-indexed: the first character in the line has an offset of 1.
The source code text involved in the error.
Which line number in the file the error occurred ends in. This is 1-indexed: the first line in the file has a lineno of 1.
The column in the end line where the error occurred finishes. This is 1-indexed: the first character in the line has an offset of 1.
For errors in f-string fields, the message is prefixed by “f-string: ” and the offsets are offsets in a text constructed from the replacement expression. For example, compiling f’Bad field’ results in this args attribute: (‘f-string: …’, (‘’, 1, 2, ‘(a b)n’, 1, 5)).
Changed in version 3.10: Added the end_lineno and end_offset attributes.
Base class for syntax errors related to incorrect indentation. This is a subclass of SyntaxError .
Raised when indentation contains an inconsistent use of tabs and spaces. This is a subclass of IndentationError .
Raised when the interpreter finds an internal error, but the situation does not look so serious to cause it to abandon all hope. The associated value is a string indicating what went wrong (in low-level terms).
You should report this to the author or maintainer of your Python interpreter. Be sure to report the version of the Python interpreter ( sys.version ; it is also printed at the start of an interactive Python session), the exact error message (the exception’s associated value) and if possible the source of the program that triggered the error.
This exception is raised by the sys.exit() function. It inherits from BaseException instead of Exception so that it is not accidentally caught by code that catches Exception . This allows the exception to properly propagate up and cause the interpreter to exit. When it is not handled, the Python interpreter exits; no stack traceback is printed. The constructor accepts the same optional argument passed to sys.exit() . If the value is an integer, it specifies the system exit status (passed to C’s exit() function); if it is None , the exit status is zero; if it has another type (such as a string), the object’s value is printed and the exit status is one.
A call to sys.exit() is translated into an exception so that clean-up handlers ( finally clauses of try statements) can be executed, and so that a debugger can execute a script without running the risk of losing control. The os._exit() function can be used if it is absolutely positively necessary to exit immediately (for example, in the child process after a call to os.fork() ).
The exit status or error message that is passed to the constructor. (Defaults to None .)
Raised when an operation or function is applied to an object of inappropriate type. The associated value is a string giving details about the type mismatch.
This exception may be raised by user code to indicate that an attempted operation on an object is not supported, and is not meant to be. If an object is meant to support a given operation but has not yet provided an implementation, NotImplementedError is the proper exception to raise.
Passing arguments of the wrong type (e.g. passing a list when an int is expected) should result in a TypeError , but passing arguments with the wrong value (e.g. a number outside expected boundaries) should result in a ValueError .
Raised when a reference is made to a local variable in a function or method, but no value has been bound to that variable. This is a subclass of NameError .
Raised when a Unicode-related encoding or decoding error occurs. It is a subclass of ValueError .
UnicodeError has attributes that describe the encoding or decoding error. For example, err.object[err.start:err.end] gives the particular invalid input that the codec failed on.
The name of the encoding that raised the error.
A string describing the specific codec error.
The object the codec was attempting to encode or decode.
The first index of invalid data in object .
The index after the last invalid data in object .
Raised when a Unicode-related error occurs during encoding. It is a subclass of UnicodeError .
Raised when a Unicode-related error occurs during decoding. It is a subclass of UnicodeError .
Raised when a Unicode-related error occurs during translating. It is a subclass of UnicodeError .
Raised when an operation or function receives an argument that has the right type but an inappropriate value, and the situation is not described by a more precise exception such as IndexError .
Raised when the second argument of a division or modulo operation is zero. The associated value is a string indicating the type of the operands and the operation.
The following exceptions are kept for compatibility with previous versions; starting from Python 3.3, they are aliases of OSError .
exception EnvironmentError ¶ exception IOError ¶ exception WindowsError ¶
Only available on Windows.
OS exceptions¶
The following exceptions are subclasses of OSError , they get raised depending on the system error code.
Raised when an operation would block on an object (e.g. socket) set for non-blocking operation. Corresponds to errno EAGAIN , EALREADY , EWOULDBLOCK and EINPROGRESS .
In addition to those of OSError , BlockingIOError can have one more attribute:
An integer containing the number of characters written to the stream before it blocked. This attribute is available when using the buffered I/O classes from the io module.
Raised when an operation on a child process failed. Corresponds to errno ECHILD .
A base class for connection-related issues.
A subclass of ConnectionError , raised when trying to write on a pipe while the other end has been closed, or trying to write on a socket which has been shutdown for writing. Corresponds to errno EPIPE and ESHUTDOWN .
A subclass of ConnectionError , raised when a connection attempt is aborted by the peer. Corresponds to errno ECONNABORTED .
A subclass of ConnectionError , raised when a connection attempt is refused by the peer. Corresponds to errno ECONNREFUSED .
A subclass of ConnectionError , raised when a connection is reset by the peer. Corresponds to errno ECONNRESET .
Raised when trying to create a file or directory which already exists. Corresponds to errno EEXIST .
Raised when a file or directory is requested but doesn’t exist. Corresponds to errno ENOENT .
Raised when a system call is interrupted by an incoming signal. Corresponds to errno EINTR .
Changed in version 3.5: Python now retries system calls when a syscall is interrupted by a signal, except if the signal handler raises an exception (see PEP 475 for the rationale), instead of raising InterruptedError .
Raised when a file operation (such as os.remove() ) is requested on a directory. Corresponds to errno EISDIR .
Raised when a directory operation (such as os.listdir() ) is requested on something which is not a directory. On most POSIX platforms, it may also be raised if an operation attempts to open or traverse a non-directory file as if it were a directory. Corresponds to errno ENOTDIR .
Raised when trying to run an operation without the adequate access rights — for example filesystem permissions. Corresponds to errno EACCES , EPERM , and ENOTCAPABLE .
Changed in version 3.11.1: WASI’s ENOTCAPABLE is now mapped to PermissionError .
Raised when a given process doesn’t exist. Corresponds to errno ESRCH .
Raised when a system function timed out at the system level. Corresponds to errno ETIMEDOUT .
New in version 3.3: All the above OSError subclasses were added.
PEP 3151 — Reworking the OS and IO exception hierarchy
Warnings¶
The following exceptions are used as warning categories; see the Warning Categories documentation for more details.
Base class for warning categories.
Base class for warnings generated by user code.
Base class for warnings about deprecated features when those warnings are intended for other Python developers.
Ignored by the default warning filters, except in the __main__ module ( PEP 565). Enabling the Python Development Mode shows this warning.
The deprecation policy is described in PEP 387.
Base class for warnings about features which are obsolete and expected to be deprecated in the future, but are not deprecated at the moment.
This class is rarely used as emitting a warning about a possible upcoming deprecation is unusual, and DeprecationWarning is preferred for already active deprecations.
Ignored by the default warning filters. Enabling the Python Development Mode shows this warning.
The deprecation policy is described in PEP 387.
Base class for warnings about dubious syntax.
Base class for warnings about dubious runtime behavior.
Base class for warnings about deprecated features when those warnings are intended for end users of applications that are written in Python.
Base class for warnings about probable mistakes in module imports.
Ignored by the default warning filters. Enabling the Python Development Mode shows this warning.
Base class for warnings related to Unicode.
Base class for warnings related to encodings.
New in version 3.10.
Base class for warnings related to bytes and bytearray .
Base class for warnings related to resource usage.
Ignored by the default warning filters. Enabling the Python Development Mode shows this warning.
New in version 3.2.
Exception groups¶
The following are used when it is necessary to raise multiple unrelated exceptions. They are part of the exception hierarchy so they can be handled with except like all other exceptions. In addition, they are recognised by except* , which matches their subgroups based on the types of the contained exceptions.
exception ExceptionGroup ( msg , excs ) ¶ exception BaseExceptionGroup ( msg , excs ) ¶
Both of these exception types wrap the exceptions in the sequence excs . The msg parameter must be a string. The difference between the two classes is that BaseExceptionGroup extends BaseException and it can wrap any exception, while ExceptionGroup extends Exception and it can only wrap subclasses of Exception . This design is so that except Exception catches an ExceptionGroup but not BaseExceptionGroup .
The BaseExceptionGroup constructor returns an ExceptionGroup rather than a BaseExceptionGroup if all contained exceptions are Exception instances, so it can be used to make the selection automatic. The ExceptionGroup constructor, on the other hand, raises a TypeError if any contained exception is not an Exception subclass.
The msg argument to the constructor. This is a read-only attribute.
A tuple of the exceptions in the excs sequence given to the constructor. This is a read-only attribute.
Returns an exception group that contains only the exceptions from the current group that match condition, or None if the result is empty.
The condition can be either a function that accepts an exception and returns true for those that should be in the subgroup, or it can be an exception type or a tuple of exception types, which is used to check for a match using the same check that is used in an except clause.
The nesting structure of the current exception is preserved in the result, as are the values of its message , __traceback__ , __cause__ , __context__ and __notes__ fields. Empty nested groups are omitted from the result.
The condition is checked for all exceptions in the nested exception group, including the top-level and any nested exception groups. If the condition is true for such an exception group, it is included in the result in full.
Like subgroup() , but returns the pair (match, rest) where match is subgroup(condition) and rest is the remaining non-matching part.
Returns an exception group with the same message , but which wraps the exceptions in excs .
This method is used by subgroup() and split() . A subclass needs to override it in order to make subgroup() and split() return instances of the subclass rather than ExceptionGroup .
subgroup() and split() copy the __traceback__ , __cause__ , __context__ and __notes__ fields from the original exception group to the one returned by derive() , so these fields do not need to be updated by derive() .
Note that BaseExceptionGroup defines __new__() , so subclasses that need a different constructor signature need to override that rather than __init__() . For example, the following defines an exception group subclass which accepts an exit_code and and constructs the group’s message from it.
Like ExceptionGroup , any subclass of BaseExceptionGroup which is also a subclass of Exception can only wrap instances of Exception .
Демистификация Ошибки Атрибута Python С Примерами
Ошибки – неотъемлемая часть жизни программиста. И это совсем не плохо, если вы получаете ошибку. Получение ошибки означает, что вы изучаете что-то новое. Но мы должны устранить эти ошибки. И прежде чем решить эту ошибку, мы должны знать, почему мы получаем эту ошибку. В python есть некоторые часто встречающиеся ошибки, такие как Ошибка типа , Синтаксическая ошибка, Ошибка ключа, Ошибка атрибута, Ошибка имени, и так далее.
В этой статье мы узнаем о том, что такое python AttributeError, почему мы его получаем и как его разрешаем? Интерпретатор Python вызывает AttributeError, когда мы пытаемся вызвать или получить доступ к атрибуту объекта, но этот объект не обладает этим атрибутом. Например, Если мы попытаемся использовать функцию upper() для целого числа, то получим ошибку атрибута.
Почему мы Получаем AttributeError?
Всякий раз, когда мы пытаемся получить доступ к атрибуту, который не принадлежит этому объекту, мы получаем attributeerror. Например, Мы знаем, что для того, чтобы сделать строку прописной, мы используем upper().
Здесь мы пытаемся преобразовать целое число в заглавную букву, что невозможно, поскольку целые числа не приписывают быть верхними или нижними. Но если попытаться использовать эту функцию upper() для строки, мы получим результат, потому что строка может быть квалифицирована как верхняя или нижняя.
Некоторые распространенные ошибки, которые приводят к ошибке атрибута в python
Если мы попытаемся выполнить append() для любого типа данных, отличного от List:
Иногда, когда мы хотим объединить две строки, мы пытаемся добавить одну строку в другую, что невозможно, и мы получаем ошибку атрибута.
То же самое относится и к кортежам,
Попытка доступа к атрибуту класса:
Иногда мы пытаемся получить доступ к атрибутам класса, которыми он не обладает. Давайте лучше разберемся в этом на примере.
Здесь у нас есть два класса — один-класс человека, а другой — класс транспортного средства. Оба обладают разными свойствами.
В приведенных выше примерах, когда мы попытались получить доступ к свойству пола класса Person, нам это удалось. Но когда мы попытались получить доступ к атрибуту engine_type (), он показал нам ошибку. Это происходит потому, что у человека нет атрибута под названием engine_type. Точно так же, когда мы попытались вызвать engine_type на транспортном средстве, мы добились успеха, но это было не в случае пола, так как Транспортное средство не имеет атрибута, называемого полом.
AttributeError: ‘NoneType’
Мы получаем ошибку NoneType, когда получаем «None» вместо экземпляра, который, как мы предполагаем, мы получим. Это означает, что задание провалилось или вернуло неожиданный результат.
При работе с модулями:
Очень часто при работе с модулями возникает ошибка атрибута. Предположим, мы импортируем модуль с именем hello и пытаемся получить доступ к двум функциям в нем. Один из них-print_name (), а другой-print_age().
Поскольку модуль hello не содержит атрибута print_age, мы получили атрибут Attributeerror. В следующем разделе мы узнаем, как устранить эту ошибку.
Как разрешить AttributeError в Python
Используйте справку():
Разработчики python пытались решить любую возможную проблему, с которой сталкиваются программисты Python. В этом случае также, если мы путаемся в том, принадлежит ли конкретный атрибут объекту или нет, мы можем использовать help(). Например, если мы не знаем, можем ли мы использовать append() для строки, мы можем print(help(str)) знать все операции, которые мы можем выполнять со строками. Не только эти встроенные типы данных, но мы также можем использовать help() для пользовательских типов данных, таких как Class.
Например, если мы не знаем, какими атрибутами обладает класс Person, объявленный нами выше,
Разве это не здорово! Это именно те атрибуты, которые мы определили в нашем классе Персон.
Теперь давайте попробуем использовать help() для нашего модуля hello внутри модуля hi.
Использование оператора Try – Except
Очень <сильный>профессиональный способ справиться не только с атрибутивной ошибкой, но и с любой ошибкой-это использовать try-except операторы. Если мы думаем, что можем получить ошибку в определенном блоке кода, мы можем заключить их в href=»https://en.wikipedia.org/wiki/Exception_handling»>попробуйте заблокировать. Давайте посмотрим, как это сделать. href=»https://en.wikipedia.org/wiki/Exception_handling»>попробуйте заблокировать. Давайте посмотрим, как это сделать.
Предположим, мы не уверены, содержит ли класс Person атрибут engine_type или нет, мы можем заключить его в блок try.
Должен Читать
- Как преобразовать строку в нижний регистр в
- Как вычислить Квадратный корень
- Пользовательский ввод | Функция ввода () | Ввод с клавиатуры
- Лучшая книга для изучения Python
Вывод
Всякий раз, когда мы пытаемся получить доступ к атрибуту объекта, который ему не принадлежит, мы получаем AttributeError в Python. Мы можем решить эту проблему с помощью функции help() или операторов try-except.
Попробуйте запустить программы на вашей стороне и дайте нам знать, если у вас есть какие-либо вопросы.
Python AttributeError: A How-To Guide
Attributes are values or functions associated with an object, a data type, or a class. If you call an attribute on a value whose data type or class does not support that attribute, you’ll encounter an AttributeError.
This guide discusses what an AttributeError is and what it means. We’ll walk through an example of an AttributeError so you can learn how to fix one in your code.
Find Your Bootcamp Match
- Career Karma matches you with top tech bootcamps
- Access exclusive scholarships and prep courses
Select your interest
First name
Last name
Phone number
By continuing you agree to our Terms of Service and Privacy Policy, and you consent to receive offers and opportunities from Career Karma by telephone, text message, and email.
What is a Python AttributeError?
A Python AttributeError is raised when you try to call an attribute of an object whose type does not support that method. For instance, trying to use the Python append() method on a string returns an AttributeError because strings do not support append().
In a Python class, you can define methods and values that are shared by the objects of that class. This is why some people think of classes as blueprints for objects.
Calling a method or a class is another way of saying you are referencing an attribute of that class. One way to think about an attribute is like a physical attribute of a person. Some people have blue eyes. Some people have pink-dyed hair. These are all attributes.
In a Python class, an attribute could be “eye_color”. This attribute could define the color of a person’s eyes. An attribute could also be a function. A function called changeEyeColor() could change the value of “eye_color”.
Data types have attributes. For instance, you can use the Python join() method to convert a string into a list. String objects support the join() method.
If you try to reference a function or a value not associated with a class object or a data type, you’ll encounter an AttributeError.
Attribute Error Python Example
Let’s write a program that merges two lists of shoes. Two shoe stores are going through a merger and want to make a list of all the unique shoes they sell.
To start, let’s define a Python set that contains the shoes from store one, Harrisons Shoes:
We use curly braces to define our set. Next, let’s define a set with the names of the shoes offered by the store that is merging with Harrisons. This shoe store is called the Shoe Emporium:
Because these two collections are sets, they can only store unique values. That means when we add them together, we’ll get a set with no duplicate values.
To add our sets together, we’re going to use the built-in function called extend():
The extend() method adds all the shoes from the “shoe_emporium” set to the “harrisons_shoes” set. We use a Python print() statement. This lets us we can see all the shoes in our new set. Let’s run our code and see what happens:
Our code returns an AttributeError.
AttributeError Python Solution
Our error message tells us we cannot use the method extend() on an object whose data type is a set. This is because extend() is a list method. It is not supported by sets.
If we want to merge our two sets, we have to use an addition sign:
This will add the contents of the “shoe_emporium” set to the “harrisons_shoes” set. We then print all the values in the “harrisons_shoes” set to the console. Let’s run our new program:
Our program returns a set with all the shoes from our two original sets. While there were six values in our original two sets, now there are only five. This is because two of the shoes were the same and sets can only store unique values.
Our program returns a set with all the shoes from our two original sets. While there were six values in our original two sets, now there are only five. This is because two of the shoes were the same and sets can only store unique values.
Similar AttributeErrors to Explore
AttributeErrors are incredibly common. They can arise when you try to call attributes of data types and classes that do not support the attribute you are referring to.
These errors may also be caused if you make a typo when referring to an attribute. Python will interpret your code as-is. If you make a typo, it will appear to Python that you are referring to an attribute that does not exist.
For instance, using the Python split() method to split a list is common. But, split() is a string method and so it cannot be used to split a list.
For further reading, consider researching the following errors:
Conclusion
Attribute errors in Python are raised when an invalid attribute is referenced. To solve these errors, first check that the attribute you are calling exists. Then, make sure the attribute is related to the object or data type with which you are working.
If the attribute you want is associated with a built-in type and does not exist, you should look for an alternative. There are alternatives for many attributes that exist for one data type you can use on another data type. For instance, there is no extend() method with sets but you can use union() to join to sets.
To learn more about writing Python code, read our How to Learn Python guide.
«Career Karma entered my life when I needed it most and quickly helped me match with a bootcamp. Two months after graduating, I found my dream job that aligned with my values and goals in life!»
Venus, Software Engineer at Rockbot
Find Your Bootcamp Match
About us: Career Karma is a platform designed to help job seekers find, research, and connect with job training programs to advance their careers. Learn about the CK publication.
Python AttributeError: A Complete Guide
Attributes are the properties and methods defined for a class, object, or data type. In Python, everything is an object. That’s why many inbuilt data types, such as list, tuple, int, float, etc., support methods and properties.
Different objects have different attribute values, for instance, the list support append() method, whereas the tuple does not. And if we try to call the append() method on a tuple object, we will receive the AttributeError with an error message that this tuple object does not have the following attribute.
This is not only with tuples and lists. For every object, whether it is an object of a user-defined class or an inbuilt data type, if we try to access an unsupported attribute(property or method) on that object, we will encounter the AttributeError.
In this Python tutorial, we will discuss what AttributeError is and why it occurs in a Python program.
What is Python AttributeError ?
AttributeError is one of Python’s standard exceptions. And as a Python developer, you will encounter this error many times. But once you know why this error is raised in your program, you will be able to solve it in no time. Before we discuss the AttributeError, let’s take a look at what an attribute is.
What are Attributes?
Attributes are the properties and methods that are defined for a class or object. When we create a class using the class keywords, all the properties and methods defined inside that class will be called the class attributes. And once we define an object for that class, we can access those attributes using that object only. Similarly, built-in objects like a list, tuple, dictionary, int, float, etc., come with built-in attributes. We can list out all the supported attributes of an object using the dir() function.
Example
Output
AttributeError
To access an attribute of an object, we use the object name followed by the dot operator and the attribute name. If the attribute is a method, we also put the parenthesis » () » after the attribute name. But if we try to access such an attribute that does not exist for that object, we will receive the attribute Error.
Example 1: AttributeError with built-in Objects
Let’s say we have two containers container1 is a list object and container2 is a set object. We also have a string of which words we need to add to these two containers. As container1 is a list it can contain duplicate words but the container2 will only contain unique words.
Output
In this example, we are getting the attribute error «AttributeError: ‘set’ object has no attribute ‘append'» . This is because container2 is a set object, and it does not have any method append() . append() method is only supported by Python’s list objects. To add a new element to the set object, we use the add() method.
Example 1 solution
Output
Example 2: AttributeError class and objects
We also the attribute error when we try to access such property or method of a class that does not exist. This generally happens when we make some typos while calling a property or method.
Output
In the above example, we are getting this error because we are trying to access the bill() method that is not defined in the Order class. To solve this problem, we need to ensure that we are calling the correct method to access the price for our product. In our Order class, to get the total price, we have the price() method not bill() .
Example 2 solution
Output
Conclusion
Attribute Error is raised in a Python program when we try to access an unsupported attribute using an object. To solve the error, we need to ensure that the method or property we are trying to access through the object does support the object.
If you are getting this error with some built-in data type object and do not know all the attributes of the object. For that, you can use the Python dir() function, which will list all the attributes supported by that particular object.