Welcome to Pug’s documentation!

Pug

https://img.shields.io/pypi/v/pip-pug.svg https://img.shields.io/travis/ronpandolfi/pip-pug.svg Documentation Status Updates

A cute, lazy, interactive pip wrapper.

Credits

This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.

Installation

Stable release

To install pug, run this command in your terminal:

$ pip install pug

This is the preferred method to install pug, as it will always install the most recent stable release.

If you don’t have pip installed, this Python installation guide can guide you through the process.

From sources

The sources for pug can be downloaded from the Github repo.

You can either clone the public repository:

$ git clone git://github.com/ronpandolfi/pug

Or download the tarball:

$ curl -OJL https://github.com/ronpandolfi/pug/tarball/master

Once you have a copy of the source, you can install it with:

$ python setup.py install

Usage

You can use pug without specifying an operation. Pug shows you a selection of available packages matching that name. From this menu you can select to install/uninstall packages:

pug numpy
pug numpy

Some packages can be installed from multiple providers, and/or installed by different mechanisms. If pug finds these options, you’ll have some choices.

You can also list installed packages with:

pug

There are also some special commands Pug provides.

Refresh

The refresh command is useful when working with editable installations which include entry points. Each time a package’s entry points change, it must be reinstalled for that change to take effect, even when using editable installations. A quick and lazy way to ‘resfresh’ those packages is simply:

pug refresh

This effectively reinstalls all editable packages, updating their entry points.

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

You can contribute in many ways:

Types of Contributions

Report Bugs

Report bugs at https://github.com/ronpandolfi/pug/issues.

If you are reporting a bug, please include:

  • Your operating system name and version.
  • Any details about your local setup that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.

Fix Bugs

Look through the GitHub issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement it.

Implement Features

Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.

Write Documentation

Pug could always use more documentation, whether as part of the official pug docs, in docstrings, or even on the web in blog posts, articles, and such.

Submit Feedback

The best way to send feedback is to file an issue at https://github.com/ronpandolfi/pug/issues.

If you are proposing a feature:

  • Explain in detail how it would work.
  • Keep the scope as narrow as possible, to make it easier to implement.
  • Remember that this is a volunteer-driven project, and that contributions are welcome :)

Get Started!

Ready to contribute? Here’s how to set up pug for local development.

  1. Fork the pug repo on GitHub.

  2. Clone your fork locally:

    $ git clone git@github.com:your_name_here/pug.git

  3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:

    $ mkvirtualenv pug
$ cd pug/
$ python setup.py develop

  4. Create a branch for local development:

    $ git checkout -b name-of-your-bugfix-or-feature

    Now you can make your changes locally.

  5. When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:

    $ flake8 pug tests
$ python setup.py test or pytest
$ tox

    To get flake8 and tox, just pip install them into your virtualenv.

  6. Commit your changes and push your branch to GitHub:

    $ git add .
$ git commit -m "Your detailed description of your changes."
$ git push origin name-of-your-bugfix-or-feature

  7. Submit a pull request through the GitHub website.

Pull Request Guidelines

Before you submit a pull request, check that it meets these guidelines:

  1. The pull request should include tests.
  2. If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
  3. The pull request should work for Python 3.5, 3.6, 3.7 and 3.8, and for PyPy. Check https://travis-ci.com/ronpandolfi/pug/pull_requests and make sure that the tests pass for all supported Python versions.

Tips

To run a subset of tests:

$ pytest tests.test_pug

Deploying

A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.rst). Then run:

$ bump2version patch # possible: major / minor / patch
$ git push
$ git push --tags

Travis will then deploy to PyPI if tests pass.

Credits

Development Lead

Contributors

None yet. Why not be the first?

History

0.1.0 (2020-08-02)

  • First release on PyPI.

Indices and tables