Sudoku Solver

A web-based Sudoku solver built using Python and Python only

The motivation is to demonstrate how Backtracking algorithm works.

Some of the key highlights of this Sudoku solver app:

Ability to generate a random valid Sudoku puzzle
Solves a Sudoku puzzle using backtracking
Able to validate if a Sudoku board
Hosted using Google App Engine

Development

Installation

Make sure you have poetry installed on your machine.

poetry install

# Optional: Installing dependencies only
poetry install --no-root

# Optional: Updating dependencies to their latest versions
poetry update

Setup Pre-commit Hooks

Before you begin your development work, make sure you have installed pre-commit hooks.

Some example useful invocations:

pre-commit install: Default invocation. Installs the pre-commit script alongside any existing git hooks.
pre-commit install --install-hooks --overwrite: Idempotently replaces existing git hook scripts with pre-commit, and also installs hook environments.
pre-commit run: Run hooks.

Usage

To run on debug mode locally on your browser:

poetry run python3 main.py --debug=True --port=8080

Then, visit http://localhost:8080/ on your browser.

Deployment

This section is only required if you intend to deploy to GAE.

For reference, do check this out.

Dependencies

Configure all dependencies you will need for your web service in your requirements.txt file.

# This command exports the poetry lock file to other formats.
poetry export -f requirements.txt --output requirements.txt

Google App Engine

# To deploy app configuration
gcloud init
gcloud app deploy app.yml --project xxx

# Optional: To stream logs
gcloud app logs tail -s default

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Steps

Fork this
Create your feature branch (git checkout -b feature/fooBar)
Please make sure you have installed the pre-commit hook and make sure it passes all the lint and format check
Commit your changes (git commit -am 'Add some fooBar')
Push to the branch (git push origin feature/fooBar)
Create a new Pull Request

References

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

.github/workflows/ci.yml (github-actions)
requirements.txt (pip_requirements)
pyproject.toml (poetry)

Configuration Summary

Based on the default config's presets, Renovate will:

Start dependency updates only once this onboarding PR is merged
Enable Renovate Dependency Dashboard creation
If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
Ignore node_modules, bower_components, vendor and various test/tests directories
Autodetect whether to pin dependencies or maintain ranges
Rate limit PR creation to a maximum of two per hour
Limit to maximum 10 open PRs at any time
Group known monorepo packages together
Use curated list of recommended non-monorepo package groupings
Fix some problems with very old Maven commons versions
Ignore spring cloud 1.x releases
Ignore web3j 5.0.0 release
Ignore http4s digest-based 1.x milestones
Use node versioning for @types/node
Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
Do not upgrade from Alpine stable to edge

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

Update abatilo/actions-poetry action to v2.1.4

Schedule: ["at any time"]
Branch name: renovate/abatilo-actions-poetry-2.x
Merge into: main
Upgrade abatilo/actions-poetry to v2.1.4

Update dependency pywebio to v1.6.1

Schedule: ["at any time"]
Branch name: renovate/pywebio-1.x
Merge into: main
Upgrade pywebio to ==1.6.1

Update actions/checkout action to v3

Schedule: ["at any time"]
Branch name: renovate/actions-checkout-3.x
Merge into: main
Upgrade actions/checkout to v3

Update actions/setup-python action to v3

Schedule: ["at any time"]
Branch name: renovate/actions-setup-python-3.x
Merge into: main
Upgrade actions/setup-python to v3

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate. View repository job log here.

☘️ Projet Voltaire Solver in Python3

8 Dec 2, 2022

Dot Browser is a privacy-conscious web browser with smarts built-in for protection against trackers and advertisments online.

🌍 Take back your privacy with Dot Browser, the privacy-conscious web browser that protects you from being tracked and monitored online.

1k Jan 7, 2023

Configure Renovate
Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

.github/workflows/ci.yml (github-actions)

requirements.txt (pip_requirements)

pyproject.toml (poetry)

Configuration Summary

Based on the default config's presets, Renovate will:

Start dependency updates only once this onboarding PR is merged

Enable Renovate Dependency Dashboard creation

If semantic commits detected, use semantic commit type fix for dependencies and chore for all others

Ignore node_modules, bower_components, vendor and various test/tests directories

Autodetect whether to pin dependencies or maintain ranges

Rate limit PR creation to a maximum of two per hour

Limit to maximum 10 open PRs at any time

Group known monorepo packages together

Use curated list of recommended non-monorepo package groupings

Fix some problems with very old Maven commons versions

Ignore spring cloud 1.x releases

Ignore web3j 5.0.0 release

Ignore http4s digest-based 1.x milestones

Use node versioning for @types/node

Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133

Do not upgrade from Alpine stable to edge

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

Update abatilo/actions-poetry action to v2.1.4

Schedule: ["at any time"]

Branch name: renovate/abatilo-actions-poetry-2.x

Merge into: main

Upgrade abatilo/actions-poetry to v2.1.4

Update dependency pywebio to v1.6.1

Schedule: ["at any time"]

Branch name: renovate/pywebio-1.x

Merge into: main

Upgrade pywebio to ==1.6.1

Update actions/checkout action to v3

Schedule: ["at any time"]

Branch name: renovate/actions-checkout-3.x

Merge into: main

Upgrade actions/checkout to v3

Update actions/setup-python action to v3

Schedule: ["at any time"]

Branch name: renovate/actions-setup-python-3.x

Merge into: main

Upgrade actions/setup-python to v3

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate. View repository job log here.
opened by renovate[bot] 1