Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Massive MEP move #4293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 23 commits into from
Mar 30, 2015
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
DOC : move MEP8
  • Loading branch information
tacaswell committed Mar 28, 2015
commit e07dc2d2843417e71eac02407600ff9dd2775fbe
58 changes: 58 additions & 0 deletions 58 doc/devel/MEP/MEP08.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
============
MEP8: PEP8
============

.. contents::
:local:


Status
======

**Discussion**

Branches and Pull requests
==========================

None so far.

Abstract
========

The matplotlib codebase predates PEP8, and therefore is less than
consistent style-wise in some areas. Bringing the codebase into
compliance with PEP8 would go a long way to improving its legibility.

Detailed description
====================

Some files use four space indentation, some use three. Some use
different levels in the same file.

For the most part, class/function/variable naming follows PEP8, but it
wouldn't hurt to fix where necessary.

Implementation
==============

The implementation should be fairly mechanical: running the pep8 tool
over the code and fixing where appropriate.

This should be merged in after the 2.0 release, since the changes will
likely make merging any pending pull requests more difficult.

Additionally, and optionally, PEP8 compliance could be tracked by an
automated build system.

Backward compatibility
======================

Public names of classes and functions that require change (there
shouldn't be many of these) should first be deprecated and then
removed in the next release cycle.

Alternatives
============

PEP8 is a popular standard for Python code style, blessed by the
Python core developers, making any alternatives less desirable.
1 change: 1 addition & 0 deletions 1 doc/devel/MEP/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ Matplotlib Enhancement Proposals
:maxdepth: 1

template
MEP08
MEP10
MEP11
MEP12
Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.