About
This Python package provides support for custom contests on the Timus Online Judge.
Define the players and problems to get an automatically-updating score board which is generated according to the ACM ICPC rules.
The sample output is available for preview.
Configuration
timus.scoreboard uses INI-style files for configuration. Here is a sample configuration:
[contest] title = My sample contest start = 12:00:00 1 Oct 2012 end = 17:00:00 1 Oct 2012 [users] 1000 = Team 1 (John, Jack, Suzan) 1001 = Team 2 (Mike, Roger, Dan) [problems] 1000 = A 1001 = B 1002 = C 1003 = D [config] output_dir = ./output
The values for contest section do not require an explanation. Just be sure to stick to the date format used and remember that the Timus Online Judge is operating in UTC+6 time zone.
Next, list the user IDs and their names in the users section. The ID is the numerical part of your Judge ID. The remaining letters should be kept secret and not entered in the configuration. This means that if you’re organizing a contest, the IDs must be collected beforehand. It should be noted that while contestants may have specified their names in the Timus system, you will have to specify official names (e.g. containing the last names of team members) in the configuration file.
Problems must be entered in the problems section. In the Timus system, problems have names, but for an ACM-style contest you will want to have short names (A/B/C/… is a standard).
Running timus-scoreboard
After installing timus.scoreboard egg, you should be able to execute the timus-scoreboard script. The location of this script depends on the way you installed the egg. For instance, if zc.buildout was used, the script will reside in bin directory as generated by buildout.
The script requires the name of the configuration file as a parameter:
wormhole:timus-scoreboard admp$ bin/timus-scoreboard -n sample.conf Retrieving http://acm.timus.ru/status.aspx?count=100... Writing ./output/index.html... Writing ./output/top.html... Writing ./output/table.html...
If you, however, omit the -n option, the script will keep running until the contest ends. This is useful if you want to update the score table every few minutes.
Metadata
Release files for timus.scoreboard 0.2
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 |
|---|---|---|---|---|
| timus.scoreboard-0.2.tar.gz | 6.7 kB | Without provenance | Details for timus.scoreboard-0.2.tar.gz |
Release files / timus.scoreboard-0.2.tar.gz
| Download URL | timus.scoreboard-0.2.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75d59dcaf511f6e92ab6c52700c5f46b3119ec10c5cb074032c7a1d0d7126995
|
|
BLAKE2b-256 checksum How to use checksums |
de413be688f13e0bc047d5d192f6fa51402b4d1df61ce96c4dae119744b15d1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for timus.scoreboard 0.2
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.