| Oct | NOV | Dec |
| 09 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Collection: Archive Team: URLs
| Code | Description |
|---|---|
inherit-non-class |
Attempted to inherit something that is not a class. |
too-many-function-arguments |
Too many arguments have been provided to a function call. |
too-many-positional-arguments-before-star |
Too many arguments have been provided before a starred argument. |
no-cls-argument |
First parameter in a class method must be cls |
no-method-argument |
Method has no arguments |
no-self-argument |
First parameter in a method must be self |
parameter-already-specified |
A argument with this name has already been specified. |
parameter-missing |
A required positional argument is missing. |
positional-argument-after-keyword |
A positional argument has been provided after a keyword argument. |
positional-only-named |
A positional-only argument (3.8+) has been named in a function call. |
return-in-init |
Encountered an explicit return in __init__ function. |
typing-generic-arguments |
An error occurred while constructing Generic. |
typing-newtype-arguments |
An error occurred while constructing NewType. |
typing-typevar-arguments |
An error occurred while constructing TypeVar. |
unknown-parameter-name |
The keyword argument name provided is unknown. |
unresolved-import |
An import cannot be resolved, and may be missing. |
undefined-variable |
A variable has been used that has not yet been defined. |
variable-not-defined-globally |
A variable is not defined in the global scope. |
variable-not-defined-nonlocal |
A variable is not defined in non-local scopes. |
settings.json, but other
clients would send this via workspace/didChangeConfiguration.
Ifpython.linting.enabled is set to false in the user configuration, then no diagnostics
will be collected other than syntax errors and unresolved imports.
To control the visibility and severity of the diagnotics, there are a number of lists
that can be set in the user configuration which make use of each diagnostic's error code.
| Setting | Description |
|---|---|
python.analysis.errors |
Diagnostics which should be shown as errors. |
python.analysis.warnings |
Diagnostics which should be shown as warnings. |
python.analysis.information |
Diagnostics which should be shown as informational. |
python.analysis.disabled |
Diagnotics which should not be shown at all. |
{
"python.analysis.errors": ["undefined-variable"],
"python.analysis.warnings": ["unknown-parameter-name"],
"python.analysis.information": ["unresolved-import"],
"python.analysis.disabled": ["too-many-function-arguments", "parameter-missing"],
}
Linting can also be controlled on an individual line basis with a generalized #noqa. Lines with #noqa will have their diagnostic output suppressed.
An example usage:
from python import language_server # noqa will suppress the linting message for this line
"%LOCALAPPDATA%\Microsoft\Python Language Server" (which is Environment.SpecialFolder.LocalApplicationData). Typically "C:\Users\\%USER_NAME%\AppData\Local\Microsoft\Python Language Server"
Linux
"$XDG_CACHE_HOME/Microsoft/Python Language Server", or if XDG_CACHE_HOME is not set, "$HOME/.cache/Microsoft/Python Language Server"
macOS
"$HOME/Library/Caches/Microsoft/Python Language Server"