Skip to content

Latest commit

 

History

History

python

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

Advent of Code Python Solutions

2023 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2022 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2021 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2020 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2019 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2018 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2017 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2016 Python Progress

Day Part One Part Two
Day 1 - -
Day 2 - -
Day 3 - -
Day 4 - -
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

2015 Python Progress

Day Part One Part Two
Day 1 ~0.1ms ~0.1ms
Day 2 ~0.1ms ~0.1ms
Day 3 ~0.1ms ~0.1ms
Day 4 ~268ms ~8118ms
Day 5 - -
Day 6 - -
Day 7 - -
Day 8 - -
Day 9 - -
Day 10 - -
Day 11 - -
Day 12 - -
Day 13 - -
Day 14 - -
Day 15 - -
Day 16 - -
Day 17 - -
Day 18 - -
Day 19 - -
Day 20 - -
Day 21 - -
Day 22 - -
Day 23 - -
Day 24 - -
Day 25 - -

Setup

Have pipenv installed using pip (System packages such as the one in the debian repositories can cause bugs and are not always up to date)

pip install pipenv

Create virtualenv and install dependencies using pipenv.

For better integration with VS Code the venv is created inside the project as the interpreter is already selected in the settings.json file

pipenv install -d

If pipenv wants to use the global python version instead of pyenvs, make sure PYENV_HOME is set to $(pyenv root). Otherwise you can just force an interpreter onto pyenv using the --python argument.

pipenv install --python "$(command -v python)"

Activate the environment:

pipenv shell

Run single solution

The Current File (Python) VS Code launch config will run and debug the focused file, and loads the .env environment beforehand.

You can run manually too from the command line, but don't forget to activate the virtual environment using pipenv.

pipenv shell
python year2015/day01/p1.py

Test

Full test suite

pipenv run test

Lint

pipenv run lint

Notes

Refactoring in VS Code doesn't seem to work.

It can use the pipenv environment if you select it but it writes it into the settings.json with a full local path