You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/11/28 19:24:09 UTC

[Apache Bloodhound] BloodhoundDevGuide modified

Page "BloodhoundDevGuide" was changed by gjm
Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundDevGuide?action=diff&version=3>
Revision 3
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: BloodhoundDevGuide
=========================================================================
--- BloodhoundDevGuide (version: 2)
+++ BloodhoundDevGuide (version: 3)
@@ -1,7 +1,7 @@
 = Bloodhound Developer Guidelines =
 
 == Coding Style ==
-The coding style for Bloodhound is the [http://www.python.org/peps/pep-0008.html PEP 8] standard. Deviations from this coding style may be considered in submitted patches as readability is considered more important.
+The coding style for Python within the project is the [pep:0008 PEP 8] standard. Deviations from this coding style may be considered in submitted patches as readability is considered more important.
 
 == Ticket Work Guidelines ==
 Discussion of defects (bugs), new or improved features (enhancements) and other tasks should occur primarily on the !bloodhound-dev@incubator.apache.org mailing list. It is therefore essential that you are subscribed to this list. In general, to work on an Apache Bloodhound ticket, you would also be expected to have an account on this issue tracker so that a ticket can be assigned to you, discouraging others from duplicating your effort.
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundDevGuide>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundDevGuide' page.
If it was not you, please report to .