[](https://github.com/FollowTheProcess/pytoil)
[](https://pypi.python.org/pypi/pytoil)
[](https://github.com/FollowTheProcess/pytoil)
[](https://github.com/pypa/hatch)
[](https://github.com/astral-sh/ruff)
[](https://github.com/FollowTheProcess/pytoil/actions?query=workflow%3ACI)
[](https://codecov.io/gh/FollowTheProcess/pytoil)
[](https://results.pre-commit.ci/latest/github/FollowTheProcess/pytoil/main)
[](https://pepy.tech/project/pytoil)
> ***toil:***
> *"Long, strenuous or fatiguing labour"*
* **Source Code**: [https://github.com/FollowTheProcess/pytoil](https://github.com/FollowTheProcess/pytoil)
* **Documentation**: [https://FollowTheProcess.github.io/pytoil/](https://FollowTheProcess.github.io/pytoil/)
## What is it?
*pytoil is a small, helpful CLI to take the toil out of software development!*
`pytoil` is a handy tool that helps you stay on top of all your projects, remote or local. It's primarily aimed at python developers but you could easily use it to manage any project!
pytoil is:
* Easy to use ✅
* Easy to configure ✅
* Safe (it won't edit your repos at all) ✅
* Snappy (it's asynchronous from the ground up and as much as possible is done concurrently, clone all your repos in seconds!) 💨
* Useful! (I hope 😃)
Say goodbye to janky bash scripts 👋🏻
## Background
Like many developers I suspect, I quickly became bored of typing repeated commands to manage my projects, create virtual environments, install packages, fire off `cURL` snippets to check if I had a certain repo etc.
So I wrote some shell functions to do some of this for me...
And these shell functions grew and grew and grew.
Until one day I saw that the file I kept these functions in was over 1000 lines of bash (a lot of `printf`'s so it wasn't all logic but still). And 1000 lines of bash is *waaaay* too much!
And because I'd basically hacked it all together, it was **very** fragile. If a part of a function failed, it would just carry on and wreak havoc! I'd have to do `rm -rf all_my_projects`... I mean careful forensic investigation to fix it.
So I decided to make a robust CLI with the proper error handling and testability of python, and here it is! 🎉
## Installation
As pytoil is a CLI program, I'd recommend installing with [pipx].
```shell
pipx install pytoil
```
You can always fall back to pip
pytoil will install everything it needs *in python* to work. However, it's full feature set can only be accessed if you have the following external dependencies:
* [git]
* [conda] (if you work with conda environments)
* A directory-aware editor e.g. [VSCode] etc. (if you want to use pytoil to automatically open your projects for you)
* [poetry] (if you want to create poetry environments)
* [flit] (if you want to create flit environments)
## Quickstart
`pytoil` is super easy to get started with.
After you install pytoil, the first time you run it you'll get something like this.
If you say yes, pytoil will walk you through a few questions and fill out your config file with the values you enter. If you'd rather not do this interactively, just say no and it will instead put a default config file in the right place for you to edit later.
Once you've configured it properly, you can do things like...
#### See your local and remote projects
#### See which ones you have on GitHub, but not on your computer
#### Easily grab a project, regardless of where it is
This project is available on your local machine...
This one is on GitHub...
#### Create a new project and virtual environment in one go
(And include custom packages, see the [docs])
#### And even do this from a [cookiecutter] template
And loads more!
pytoil's CLI is designed such that if you don't specify any arguments, it won't do anything! just show you the `--help`. This is called being a 'well behaved' unix command line tool.
This is true for any subcommand of pytoil so you won't accidentally break anything if you don't specify arguments 🎉
And if you get truly stuck, you can quickly open pytoil's documentation with:
Check out the [docs] for more 💥
## Contributing
`pytoil` is an open source project and, as such, welcomes contributions of all kinds 😃
Your best bet is to check out the [contributing guide] in the docs!
[pipx]: https://pipxproject.github.io/pipx/
[docs]: https://FollowTheProcess.github.io/pytoil/
[contributing guide]: https://followtheprocess.github.io/pytoil/contributing/contributing.html
[git]: https://git-scm.com
[conda]: https://docs.conda.io/en/latest/
[VSCode]: https://code.visualstudio.com
[cookiecutter]: https://github.com/cookiecutter/cookiecutter
[poetry]: https://python-poetry.org
[flit]: https://flit.readthedocs.io
Raw data
{
"_id": null,
"home_page": "",
"name": "pytoil",
"maintainer": "Tom Fleet",
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": "tomfleet2018@gmail.com",
"keywords": "automation,cli,developer-tools,python",
"author": "Tom Fleet",
"author_email": "tomfleet2018@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/f7/91/38dab39587c891f5da038a38cea5a8559d315e72c76bc74d0d705d1c7242/pytoil-0.40.0.tar.gz",
"platform": null,
"description": "\n\n[](https://github.com/FollowTheProcess/pytoil)\n[](https://pypi.python.org/pypi/pytoil)\n[](https://github.com/FollowTheProcess/pytoil)\n[](https://github.com/pypa/hatch)\n[](https://github.com/astral-sh/ruff)\n[](https://github.com/FollowTheProcess/pytoil/actions?query=workflow%3ACI)\n[](https://codecov.io/gh/FollowTheProcess/pytoil)\n[](https://results.pre-commit.ci/latest/github/FollowTheProcess/pytoil/main)\n[](https://pepy.tech/project/pytoil)\n\n> ***toil:***\n> *\"Long, strenuous or fatiguing labour\"*\n\n* **Source Code**: [https://github.com/FollowTheProcess/pytoil](https://github.com/FollowTheProcess/pytoil)\n\n* **Documentation**: [https://FollowTheProcess.github.io/pytoil/](https://FollowTheProcess.github.io/pytoil/)\n\n\n\n## What is it?\n\n*pytoil is a small, helpful CLI to take the toil out of software development!*\n\n`pytoil` is a handy tool that helps you stay on top of all your projects, remote or local. It's primarily aimed at python developers but you could easily use it to manage any project!\n\npytoil is:\n\n* Easy to use \u2705\n* Easy to configure \u2705\n* Safe (it won't edit your repos at all) \u2705\n* Snappy (it's asynchronous from the ground up and as much as possible is done concurrently, clone all your repos in seconds!) \ud83d\udca8\n* Useful! (I hope \ud83d\ude03)\n\nSay goodbye to janky bash scripts \ud83d\udc4b\ud83c\udffb\n\n## Background\n\nLike many developers I suspect, I quickly became bored of typing repeated commands to manage my projects, create virtual environments, install packages, fire off `cURL` snippets to check if I had a certain repo etc.\n\nSo I wrote some shell functions to do some of this for me...\n\nAnd these shell functions grew and grew and grew.\n\nUntil one day I saw that the file I kept these functions in was over 1000 lines of bash (a lot of `printf`'s so it wasn't all logic but still). And 1000 lines of bash is *waaaay* too much!\n\nAnd because I'd basically hacked it all together, it was **very** fragile. If a part of a function failed, it would just carry on and wreak havoc! I'd have to do `rm -rf all_my_projects`... I mean careful forensic investigation to fix it.\n\nSo I decided to make a robust CLI with the proper error handling and testability of python, and here it is! \ud83c\udf89\n\n## Installation\n\nAs pytoil is a CLI program, I'd recommend installing with [pipx].\n\n```shell\npipx install pytoil\n```\n\n\n\nYou can always fall back to pip\n\n\n\npytoil will install everything it needs *in python* to work. However, it's full feature set can only be accessed if you have the following external dependencies:\n\n* [git]\n* [conda] (if you work with conda environments)\n* A directory-aware editor e.g. [VSCode] etc. (if you want to use pytoil to automatically open your projects for you)\n* [poetry] (if you want to create poetry environments)\n* [flit] (if you want to create flit environments)\n\n## Quickstart\n\n`pytoil` is super easy to get started with.\n\nAfter you install pytoil, the first time you run it you'll get something like this.\n\n\n\nIf you say yes, pytoil will walk you through a few questions and fill out your config file with the values you enter. If you'd rather not do this interactively, just say no and it will instead put a default config file in the right place for you to edit later.\n\nOnce you've configured it properly, you can do things like...\n\n#### See your local and remote projects\n\n\n\n#### See which ones you have on GitHub, but not on your computer\n\n\n\n#### Easily grab a project, regardless of where it is\n\nThis project is available on your local machine...\n\n\n\nThis one is on GitHub...\n\n\n\n#### Create a new project and virtual environment in one go\n\n\n\n(And include custom packages, see the [docs])\n\n#### And even do this from a [cookiecutter] template\n\n\n\nAnd loads more!\n\npytoil's CLI is designed such that if you don't specify any arguments, it won't do anything! just show you the `--help`. This is called being a 'well behaved' unix command line tool.\n\nThis is true for any subcommand of pytoil so you won't accidentally break anything if you don't specify arguments \ud83c\udf89\n\nAnd if you get truly stuck, you can quickly open pytoil's documentation with:\n\n\n\nCheck out the [docs] for more \ud83d\udca5\n\n## Contributing\n\n`pytoil` is an open source project and, as such, welcomes contributions of all kinds \ud83d\ude03\n\nYour best bet is to check out the [contributing guide] in the docs!\n\n[pipx]: https://pipxproject.github.io/pipx/\n[docs]: https://FollowTheProcess.github.io/pytoil/\n[contributing guide]: https://followtheprocess.github.io/pytoil/contributing/contributing.html\n[git]: https://git-scm.com\n[conda]: https://docs.conda.io/en/latest/\n[VSCode]: https://code.visualstudio.com\n[cookiecutter]: https://github.com/cookiecutter/cookiecutter\n[poetry]: https://python-poetry.org\n[flit]: https://flit.readthedocs.io\n",
"bugtrack_url": null,
"license": "Apache Software License 2.0",
"summary": "CLI to automate the development workflow.",
"version": "0.40.0",
"project_urls": {
"Documentation": "https://FollowTheProcess.github.io/pytoil/",
"Homepage": "https://github.com/FollowTheProcess/pytoil",
"Source": "https://github.com/FollowTheProcess/pytoil"
},
"split_keywords": [
"automation",
"cli",
"developer-tools",
"python"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "dda471935f33c67775de5a6d4d229213dd12851c3c501522bdc11e3db20a9b7b",
"md5": "893478833cf17a80da284c70e0766447",
"sha256": "ffdc39d5bde8c8ef994d70a98ab02662c6d31e655004fa5700baf5e64fde4630"
},
"downloads": -1,
"filename": "pytoil-0.40.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "893478833cf17a80da284c70e0766447",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 56696,
"upload_time": "2023-11-03T18:23:36",
"upload_time_iso_8601": "2023-11-03T18:23:36.680017Z",
"url": "https://files.pythonhosted.org/packages/dd/a4/71935f33c67775de5a6d4d229213dd12851c3c501522bdc11e3db20a9b7b/pytoil-0.40.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "f79138dab39587c891f5da038a38cea5a8559d315e72c76bc74d0d705d1c7242",
"md5": "c14296cd7a51c8c779ce6bd71fff4387",
"sha256": "973c3f259a6881494177fe430aece9018304b495c4f2ed216b4fbc3a4c53a292"
},
"downloads": -1,
"filename": "pytoil-0.40.0.tar.gz",
"has_sig": false,
"md5_digest": "c14296cd7a51c8c779ce6bd71fff4387",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 3703075,
"upload_time": "2023-11-03T18:23:38",
"upload_time_iso_8601": "2023-11-03T18:23:38.538713Z",
"url": "https://files.pythonhosted.org/packages/f7/91/38dab39587c891f5da038a38cea5a8559d315e72c76bc74d0d705d1c7242/pytoil-0.40.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-11-03 18:23:38",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "FollowTheProcess",
"github_project": "pytoil",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "pytoil"
}
JSON
