Jupyter Vote
Jupyter vote is a simple eduVote integration for Jupyter notebooks using IFrames.
Creating Polls
EduVote offers four types of polls, which can be created using the following methods. The parameters to these methods map directly to the query parameters of the poll URL which in turn directly configure the poll. The methods return an IFrame so it should be the last line in a cell, or the output needs to be explicitly displayed with display.
vote.choice(question: str, choices: int, *, multiple: bool = False, percent: bool = False, once: bool = False) -> IFramevote.yes_no(question: str, *, percent: bool = False, once: bool = False) -> IFramevote.cloud(question: str, *, keep: bool = False, live: bool = False, wait: int = 60) -> IFramevote.list(question: str, *, keep: bool = False, live: bool = False, wait: int = 60) -> IFrame
Parameters:
question: The question to be asked in the poll.choices: The number of choices to be provided.multiple: Whether multiple choices can be selected.percent: Whether to show the results in percent as opposed to counts.once: Whether the poll can only be answered once per device.keep: Whether to keep the cloud or list from the previous poll.live: Whether to show the results immediately or only after a manual reveal.wait: The time in seconds to wait before a device can submit another answer.
Voting
The interface for voting can be displayed using the vote.vote(id: str = None) -> IFrame method. The id parameter is optional and can be used to specify the teacher ID. If no ID is provided, the function attempts to use the ID stored in module level variable vote.vote_id.
Notes
The first time a poll is made, the credentials need to be entered in the EduVote interface. The credentials can be saved and should persist even between sessions.
The size of the IFrames can be adjusted by changing the vote.poll_iframe_args and vote.vote_iframe_args dictionaries which are passed directly to the IFrame constructor.
Metadata
Release files for jupyter-vote 0.3.0
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 |
|---|---|---|---|---|
| jupyter_vote-0.3.0.tar.gz | 2.0 kB | Without provenance | Details for jupyter_vote-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyter_vote-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for jupyter_vote-0.3.0-py3-none-any.whl |
Total release size: 4.7 kB
Release files / jupyter_vote-0.3.0.tar.gz
| Download URL | jupyter_vote-0.3.0.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a899ab307d76e5868ec882e00cda23ba11d0bb37b3ac717b0cc62bfac519943
|
|
BLAKE2b-256 checksum How to use checksums |
30cb51fa71b543b1a2a9a7c35002237f99de519251bdc3a108da7412980378a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.1 CPython/3.10.9 Windows/10
|
Release files / jupyter_vote-0.3.0-py3-none-any.whl
| Download URL | jupyter_vote-0.3.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e712f59f9648902b102b3c58bfbb6dbb229ee46ed6058249f8cc0b2830cf5c9
|
|
BLAKE2b-256 checksum How to use checksums |
e670757b2be013df8e18c45a5671fae3b137f0a7d8ad44886b48242e14e2f340
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.1 CPython/3.10.9 Windows/10
|
Security for jupyter-vote 0.3.0
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.