dwas - easier developer workflow

dwas aims to reduce the complexity in working on foreign projects while being powerful enough for developers working day in day out on the same project.

Working on any project should be friction-less, it should be easy to run tests, formatters, linters, build documentation, etc, from a single CLI that is discoverable and easy to use, while being powerful enough for power users.

dwas aims to provide all of this and while making environments more reproducible and isolated, without forcing the use of a containerization environment for this.

Note

Currently, dwas is very focused on python, but there are aims to make it more generic and useful for other languages, or projects that do not need virtual environments.

Getting started

If you are new to dwas, the following documentations would be the best place to start, it will get you up and running:

• Installation

• Getting Started

• Using the CLI

And the Glossary might be useful if you have terms that you do not understand in the current context.

Getting in touch

Encountering issues with dwas? Found a bug? Have suggestions for improvements? Please feel free to get in touch and submit an issue or add your point of view or additional information on an existing one if relevant.

Want to contribute? Please see our contributing guide.

Public API

Once you have installed dwas, and if you want to write your own dwasfile.py, this is the public API that is provided:

dwas	Everything explicitly exposed here is part of the dwas public API.
dwas.predefined	This module contains common predefined steps to help reduce duplication.

Other resources

dwas exists in a rich ecosystem, with plenty of high quality tools available. If dwas does not fit exactly your needs, maybe one of the following ones might. They were all influential with regards to dwas design:

• tox, is a generic virtual environment management and test command line tool that is highly tailored for python project development. It is very similar to dwas and provides good isolation of environments. However, it relies on configuration and not code to describe environments and does not handle some constructs that dwas provides, like automatically running dependencies of environments (or, as dwas calls them, steps).

• nox is similar in spirit to both dwas and tox, and, like dwas, it relies on a python file to configure environments. It however does not provide as good isolation by default as dwas does, and does not handle parallel tasks as well.

• Invoke is a more general-purpose task execution library, and is more similar to Make in that regard. It however, does not provide any predefined tasks, specific to some workflows, like dwas does.