Skip to content
Matthieu Dartiailh edited this page Mar 9, 2015 · 6 revisions

Python 2/3 support:

Labpy projects target Python 2.7 and > 3.3. It uses future for python 2/3 interoperability. Aggressive optimizations such as the use of future.utils.iteritems or future.utils.viewitems for small dictionaries are to be avoided.

Style rules : (as decided by the @Labpy-owners)

  1. all code should follow PEP 8
  2. docstrings follow Numpy convention

Git rules :

(@hgrecco: This is still being discussed, so please feel free to comment at the bottom until we reach an agreement and we merge it)

In order to keep LabPy repos in good shape, we will follow certain rules:

  1. Development will ALWAYS occur in the users fork even if a user has commit privileges.
  2. Users' forks are considered private and therefore can be rebased at any time.
  3. Commits should be reorganized into logical chunks before merging.
  4. When a commit/group of commits is ready, it will be merged into LabPy via a PR.
  5. We will let some times for other to comment on the PR.
  6. Users will rebase (not merge) to keep their forks in sync.
Clone this wiki locally