Welcome to python_cheatsheet’s documentation!

python_cheatsheet

https://img.shields.io/pypi/v/python_cheatsheet.svg https://img.shields.io/travis/davewd/python_cheatsheet.svg Documentation Status Updates

A-Z Python Cheatsheet

Features

  • Sphinx Documentation!
  • TODO

Credits

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

Installation

Stable release

To install python_cheatsheet, run this command in your terminal:

$ pip install python_cheatsheet

This is the preferred method to install python_cheatsheet, 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 python_cheatsheet can be downloaded from the Github repo.

You can either clone the public repository:

$ git clone git://github.com/davewd/python_cheatsheet

Or download the tarball:

$ curl  -OL https://github.com/davewd/python_cheatsheet/tarball/master

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

$ python setup.py install

Usage

To use python_cheatsheet in a project:

import python_cheatsheet

python_cheatsheet

python_cheatsheet package

Module contents

python_cheatsheet.a.public_fn_with_googley_docstring(name, state=None)[source]

This function does something.

Args:
name (str): The name to use.
Kwargs:
state (bool): Current state to be in.
Returns:

int. The return code:

0 -- Success!
1 -- No good.
2 -- Try again.
Raises:
AttributeError, KeyError

A really great idea. A way you might use me is

>>> print public_fn_with_googley_docstring(name='foo', state=None)
0

BTW, this always returns 0. NEVER use with MyPublicClass.

Main module.

Main module.

Main module.

python_cheatsheet.f.files()[source]

Main module.

Main module.

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/davewd/python_cheatsheet/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

python_cheatsheet could always use more documentation, whether as part of the official python_cheatsheet 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/davewd/python_cheatsheet/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 python_cheatsheet for local development.

  1. Fork the python_cheatsheet repo on GitHub.

  2. Clone your fork locally:

    $ git clone git@github.com:your_name_here/python_cheatsheet.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 python_cheatsheet
$ cd python_cheatsheet/
$ 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 python_cheatsheet tests
$ python setup.py test or py.test
$ 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 2.7, 3.4, 3.5 and 3.6, and for PyPy. Check https://travis-ci.org/davewd/python_cheatsheet/pull_requests and make sure that the tests pass for all supported Python versions.

Tips

To run a subset of tests:

$ py.test tests.test_python_cheatsheet

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:

$ bumpversion 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 (2018-09-10)

  • First release on PyPI.

Indices and tables