summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJulian Andres Klode <jak@debian.org>2011-05-27 15:53:24 +0200
committerJulian Andres Klode <jak@debian.org>2011-05-27 15:53:24 +0200
commitb08e19a9ce1dfae6c632831f44916cd4916d672e (patch)
treef0b86fd28a475325ecc164cbd10d9dff02838692
parentba4ba3e73303860b032ae1a1ae5c27c98e629cd6 (diff)
downloadpython-apt-b08e19a9ce1dfae6c632831f44916cd4916d672e.tar.gz
* doc/source/tutorials/contributing.rst: minor improvements (Closes: #625225)
- one typo [2to => 2to3], one broken link [pep8.py link]
-rw-r--r--debian/changelog2
-rw-r--r--doc/source/tutorials/contributing.rst6
2 files changed, 5 insertions, 3 deletions
diff --git a/debian/changelog b/debian/changelog
index 6a906324..bcdaecdc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,8 @@ python-apt (0.8.0~exp5) UNRELEASED; urgency=low
[ Tshepang Lekhonkhobe ]
* Fix get_changelog in Python 3 (Closes: #626532)
* apt/package.py: fix a few typos [formated->formatted] (Closes: #597054)
+ * doc/source/tutorials/contributing.rst: minor improvements (Closes: #625225)
+ - one typo [2to => 2to3], one broken link [pep8.py link]
-- Julian Andres Klode <jak@debian.org> Thu, 26 May 2011 18:01:57 +0200
diff --git a/doc/source/tutorials/contributing.rst b/doc/source/tutorials/contributing.rst
index 0735982b..aae7f382 100644
--- a/doc/source/tutorials/contributing.rst
+++ b/doc/source/tutorials/contributing.rst
@@ -232,12 +232,12 @@ The coding style for all code written in python is :PEP:`8`. Exceptions from
this rule are the documentation, where code is sometimes formatted differently
to explain aspects, and functions provided for 0.7 compatibility purposes.
-When writing code, use tools like pylint, pyflakes, pychecker and pep8.py from
-http://svn.browsershots.org/trunk/devtools/pep8/ to verify that your code is
+When writing code, use tools like pylint, pyflakes, pychecker and pep8.py
+(all available from Debian/Ubuntu) to verify that your code is
OK. Fix all the problems which seem reasonable, and mention the unfixed issues
when asking for merge.
-In order to make the automatic generation of Python 3 code using 2to possible,
+In order to make the automatic generation of Python 3 code using 2to3 possible,
code written in Python may not utilize any functionality unsupported by 2to3 or
deprecated as of Python 2.6.