COLLECTED BY

Organization: Archive Team

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: ArchiveBot: The Archive Team Crowdsourced Crawler

ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).

To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.

There is a dashboard running for the archivebot process at http://www.archivebot.com.

ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20231119003125/https://code.visualstudio.com/docs/python/python-web

'; document.body.appendChild(div.children[0]); } function pushCodingPackEvent(language, os) { let id = `${language}-${os}-coding-pack`; var analytics = window.vscodeAnalytics; analytics && analytics.event( 'click', 'download', id, ); }

In this article

Edit

Run and Debug Python in the Web

We are happy to announce experimental support for running Python code on the Web. To try it out, install the latest pre-release version of the Experimental - Python for the Web extension from the Marketplace. This work is based on WASM in Python, which is currently in development. To learn more about how it works and the ongoing progress, you can read Compiling Python to WebAssembly (WASM).

Prerequisites

The following prerequisites are needed to use the extension:

You need to have the GitHub Repositories extension installed.
You need to authenticate with GitHub.
You need to use a browser that supports cross-origin isolation. The extension has been tested with the Microsoft Edge and Google Chrome browsers.
You need to use the insider version of VS Code for the Web (for example https://insiders.vscode.dev/)
Your source code must be hosted either on your local file system or a GitHub repository that is accessed through the GitHub Repositories extension.
When starting VS Code for the Web, you need to add the following query parameter to the end of the URL: ?vscode-coi=.

Run Hello World

The screenshot below shows the execution of a simple Python program in the browser. The program consists of two files app.py and hello.py stored on the local file system.

Execution of Python code stored on a local disk

Start a REPL

The extension comes with an integrated Python REPL. To activate it, run the command Python WASM: Start REPL.

Start Python Repl

Debugging

There is support for debugging Python files on the Web and it uses the same UI as VS Code Desktop debugging. The features currently supported are:

Set breakpoints
Step into and out of functions
Debug across modules
Evaluate variables in the Debug Console
Debug the program in the Integrated Terminal

The screenshot below shows an active debug session. The files are hosted directly on GitHub on this sample repository.

Debugging a Python program

Create your own Python environment

The extension uses a pre-configured Python environment based on the CPython WebAssembly builds. The build used is Python-3.11.0-wasm32-wasi-16.zip.

You can create your own Python environment, including source wheel Python packages, following these steps:

Create a new GitHub repository.
Download a wasm-wasi-16 build from cpython-wasm-test/releases and expand it into the root of the repository.
To add source wheel packages, do the following:
- Create a site-packages folder in the root.
- Install the package using the following command pip install my_package --target ./site-packages. Note that you need to have a Python installation in your OS including pip.
Commit the changes.
Change the python.wasm.runtime setting to point to your GitHub repository. For example:
```
{
  "python.wasm.runtime": "https://github.com/dbaeumer/python-3.11.0"
}
```

Limitations

The Python for the Web support doesn't provide all the features available when running source code on your local machine. The major limitations in the Python interpreter are:

No socket support.
No thread support. As a consequence, there is no async support.
No pip support.
No support for native Python modules.

Acknowledgment

The work would have not been possible without the support of the Python community, who are building and maintaining the necessary WASM files of CPython.

Feedback

If you run into issues while using the Python for the Web extension, you can enter issues in the vscode-python-web-wasm repository.

1/20/2023

Oct	NOV	Mar
	19
2022	2023	2024