RobotChallenge
Robot Challenge
Summary
An attempt at Robot Challenge.
How to Install
# download and install python >=3.7 fromhttps://www.python.org/downloads/
# download source code using git
git clone https://github.com/sheecegardezi/RobotChallenge.git
cd RobotChallenge
# install create a virtual environment
python -m venv venv
# activate the virtual environment on Linux
source venv/bin/activate
# activate the virtual environment on windows
# source venv\Scripts\activate
# install the requirements
pip install -r requirements.txt
# install the software
pip install -e .
# run the tests
pytest --cov=robotchallenge -rx -s tests
Running Software Locally
robotchallenge --help
robotchallenge -f "`pwd`/tests/test_data/sample_problems.txt"
Usage of the Software
# Create a file with a new commond is each line eg. input_file.txt:
PLACE 1,2,EAST
MOVE
MOVE
LEFT
MOVE
REPORT
Output: 3,3,NORTH
# Run the software with the above file
robotchallenge -f "`pwd`/input_file.txt"
Running Software in Docker
# clone repo
git clone https://github.com/sheecegardezi/RobotChallenge.git
cd RobotChallenge
# building image locally
docker build -t robotchallenge .
# printing help
docker run -it --rm robotchallenge -h
# using existing test file
docker run -it --rm robotchallenge -f "/app/tests/test_data/sample_problems.txt"
# using new test file
docker run -it --rm -v "`pwd`/tests/test_data/sample_problems.txt":"/app/tests/test_data/sample_problems.txt" robotchallenge -f "/app/tests/test_data/sample_problems.txt"
Running Software using prebaked Docker Image
# pulling image from repo
docker image pull sheecegardezi/robotchallenge:latest
# printing help
docker run -it --rm sheecegardezi/robotchallenge:latest -h
# using existing test file
docker run -it --rm sheecegardezi/robotchallenge:latest -f "/app/tests/test_data/sample_problems.txt"
# using new test file
docker run -it --rm -v "`pwd`/tests/test_data/sample_problems.txt":"/app/tests/test_data/sample_problems.txt" sheecegardezi/robotchallenge:latest -f "/app/tests/test_data/sample_problems.txt"
Running Testing
pytest --cov=robotchallenge -rx -s tests
Metadata
Release files for robotchallenge 1.0.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 | |
|---|---|---|---|---|
| robotchallenge-1.0.1.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| robotchallenge-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / robotchallenge-1.0.1.tar.gz
| Download URL | robotchallenge-1.0.1.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa51d0eac925593d4ad44e5c9ff24d4f0a13cd0c9ae962f46dd42040c2cc1fbb
|
|
BLAKE2b-256 checksum How to use checksums |
a8aeff6da9519e9ec4224b1614defe759e138d3f32b4ad36fc964650473b1d95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.10
|
Release files / robotchallenge-1.0.1-py3-none-any.whl
| Download URL | robotchallenge-1.0.1-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d937667c7278b1c6a170668f11bad200129fb7bbc32cdb85ec648376683c3f6
|
|
BLAKE2b-256 checksum How to use checksums |
c405b9c40a70edb1e94fb0b53be093b7eb04f8bdaa29a1e5b197f951a4f50078
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Security for robotchallenge 1.0.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.