AtCoder Shell
This is the shell library to execute AtCoder submission on your commandline, for Python/PyPy user.
Basic operation
If you want to know more information about commands, execute acsh help.
(Note that the command results are output in Japanese.)
1. Installation
pip install acshell
2. Login
acsh login
# acsh lg
Your account credentials are stored for a certain period of time.
3. Create "Contest folder"
acsh load agc001
# acsh ld agc001
The "contest folder" of specified contest is created where you are currently. Each task folder is generated in the contest folder.
4. Write your code
Implement the answers in the file like agc001_a.py created in the folder for each task.
5. Run your codes with published testcases
Confirm the formats of the command arguments below.
acsh test [task] [num] [lang]
acsh check [task] [lang]
# acsh t
# acsh c
| option | required | value format |
|---|---|---|
| task | Yes | task code such as A, B |
| num | Yes (in test) |
number of testcase as integer |
| lang | x | language(python or pypy) |
6. Submit your codes
Confirm the formats of the command arguments below. Unlike the test running, you have to specify which language you submit codes as.
acsh submit [task] [lang]
# acsh s
| option | required | value format |
|---|---|---|
| task | Yes | task code such as A, B |
| lang | Yes | language(python or pypy) |
7. Confirm results of your submission
acsh recent # for recent submission
acsh status # for your contest scores
# acsh rc
# acsh rs
Additional Operations
Setup your cheat sheets
Follow the steps below to use your own prepared cheat-sheet codes,
Please check the arguments with the acsh help command.
Setup
- open the config folder by executing
acsh edit-cheat/acsh ec. - write your cheat sheets, and place the folder opened.
Usage
- execute
acsh add-cheat <task_code> <cheat_name (without extension)>so add the specified cheat file in the task folder. - write
from <filename> import <func/class name>in your code. - The cheat files will be merged with main code file when you submit.
Setup initial codes
If you want to set a template code, add initial.py in the cheat-sheet setup shown above.
Pyenv management
If you want to run codes by pypy, you should use pyenv for python version management. (This package can be run on python3.8, but you should use 3.11 for the exact debug in contests.)
- Install the latest version of
3.11.*andpypy3.10-7.3.*. - execute the command below.
pyenv A B C
- A: The Python version you usually use
- B: The version of installed
3.11.* - C: The version of installed
pypy3.10-7.3.*
Metadata
Release files for acshell 2.2.1
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 | |
|---|---|---|---|---|
| acshell-2.2.1.tar.gz | 17.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acshell-2.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.7 kB
Release files / acshell-2.2.1.tar.gz
| Download URL | acshell-2.2.1.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0dd579350b99bc1b8c281c9eb4fb88dbf93c9d1c4b5d4467613ada47f882a84
|
|
BLAKE2b-256 checksum How to use checksums |
b55ea8478102b71b3899d9e93186cb39d1d963a204935a6b562ad96990088801
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Release files / acshell-2.2.1-py3-none-any.whl
| Download URL | acshell-2.2.1-py3-none-any.whl |
|---|---|
| Size | 21.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56e1ce64dd905fd1821365210f38dd783b99110f7d5c04230115b06a4d5024ac
|
|
BLAKE2b-256 checksum How to use checksums |
5d0ee4629cf4183ed5414a50fdf4d171f4db9e05c86088b3975c7956af6b6d5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for acshell 2.2.1
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.