Let us walk on the 3-isogeny graph
Loading...
Searching...
No Matches
InvalidPyProjectBuildRequires Class Reference
Inheritance diagram for InvalidPyProjectBuildRequires:
Collaboration diagram for InvalidPyProjectBuildRequires:

Public Member Functions

None __init__ (self, *str package, str reason)
 
- Public Member Functions inherited from DiagnosticPipError
str __repr__ (self)
 
RenderResult __rich_console__ (self, Console console, ConsoleOptions options)
 

Static Public Attributes

str reference = "invalid-pyproject-build-system-requires"
 
- Static Public Attributes inherited from DiagnosticPipError
str reference
 

Additional Inherited Members

- Data Fields inherited from DiagnosticPipError
 kind
 
 reference
 
 message
 
 context
 
 note_stmt
 
 hint_stmt
 
 link
 

Detailed Description

Raised when pyproject.toml an invalid `build-system.requires`.

Definition at line 208 of file exceptions.py.

Constructor & Destructor Documentation

◆ __init__()

None __init__ (   self,
*str  package,
str  reason 
)

Reimplemented from DiagnosticPipError.

Definition at line 213 of file exceptions.py.

213 def __init__(self, *, package: str, reason: str) -> None:
214 super().__init__(
215 message=f"Can not process {escape(package)}",
216 context=Text(
217 "This package has an invalid `build-system.requires` key in "
218 f"pyproject.toml.\n{reason}"
219 ),
220 note_stmt="This is an issue with the package mentioned above, not pip.",
221 hint_stmt=Text("See PEP 518 for the detailed specification."),
222 )
223
224
for i

References InvalidPyProjectBuildRequires.__init__(), and i.

Referenced by InvalidPyProjectBuildRequires.__init__(), and Protocol.__init_subclass__().

Here is the call graph for this function:
Here is the caller graph for this function:

Field Documentation

◆ reference

str reference = "invalid-pyproject-build-system-requires"
static

Definition at line 211 of file exceptions.py.

Referenced by DiagnosticPipError.__init__().


The documentation for this class was generated from the following file: