Introduction
The Open Shakespeare package provides a full open set of shakespeare’s works (often in multiple versions) along with ancillary material, a variety of tools and a python API.
Specifically in addition to the works themselves (often in multiple versions) there is an introduction, a chronology, explanatory notes, a concordance and search facilities.
All material is open source/open knowledge so that anyone can use, redistribute and reuse these materials freely. For exact details of the license under which this package is made available please see COPYING.txt.
Open Shakespeare has been developed under the aegis of the Open Knowledge Foundation (http://www.okfn.org/).
Contact the Project
Please mail info@okfn.org or join the okfn-discuss mailing list:
Installation and Setup
1. Install the code
1.1: (EITHER) Install using setup.py (preferred)
Install shakespeare using easy_install:
easy_install shakespeare
NB: If you don’t have easy_install you can get from here:
<http://peak.telecommunity.com/DevCenter/EasyInstall#installation-instructions>
1.2 (OR) Get the code straight from subversion
Check out the subversion trunk:
svn co https://knowledgeforge.net/shakespeare/svn/trunk
Do:
sudo python setup.py develop
Getting Started
As a user:
1. Basic setup
To access most of the main features of Open Shakespeare you need a database. For this an other bits and bobs of configuration you will need a configuration file.
You can make a config file as follows:
paster make-config shakespeare {your-config.ini}
Tweak the config file as appropriate and then setup the application:
paster setup-app config.ini
[TODO: this should be part of setup-app]
Run:
$ shakespeare-admin db init
2. Extras
Search index. [TODO]
2. You can start a web server to provide a easy-to-use web interface to the shakespeare material and facilities by doing:
$ paster serve {your-config.ini}
NB: {your-config.ini} should be replaced with the name of the config file you created earlier.
As a developer:
0. Setup
Follow the basic steps above put with an ini file named: development.ini
NB: you’ll probably want to change log levels to debug.
1. Check out the administrative commands
$ bin/shakespeare-admin help.
2. Run the tests using either py.test of nosetests::
$ nosetests shakespeare
Metadata
Release files for shakespeare 0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| shakespeare-0.6.tar.gz | 5.4 MB | Without provenance | Details for shakespeare-0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| shakespeare-0.6-py2.5.egg | Legacy Egg format | - | - | Details for shakespeare-0.6-py2.5.egg |
Total release size: 9.8 MB
Release files / shakespeare-0.6.tar.gz
| Download URL | shakespeare-0.6.tar.gz |
|---|---|
| Size | 5.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f393d09d07ea4d0e19957838046b3601ad09e0a5bd1c5ad0454240eacff393be
|
|
BLAKE2b-256 checksum How to use checksums |
a445699c3869c2590579d0ef89df3cbd28b17eb77a14dd9f1841c51cd7d4dc1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / shakespeare-0.6-py2.5.egg
| Download URL | shakespeare-0.6-py2.5.egg |
|---|---|
| Size | 4.4 MB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
296e6eae76c8ff62e10ca0d206da4743f7f462106fc39c576abddfddd3f6d90a
|
|
BLAKE2b-256 checksum How to use checksums |
fb815ccd99cda5afcb8e36c1542f38ad79d35a1681ecd4b4cc70b1520d6a241d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for shakespeare 0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.