This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SQLObject development repository".
The branch, master has been updated
via 7141e586c7702fde769ea286864a1655ff900bf5 (commit)
via b85b7c37b1c12a727c5c16cef0564dd32a558abb (commit)
from 2686101c67dc05258a9aa3855367ebdad28ebee1 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://sourceforge.net/p/sqlobject/sqlobject/ci/7141e586c7702fde769ea286864a1655ff900bf5
commit 7141e586c7702fde769ea286864a1655ff900bf5
Author: Oleg Broytman <ph...@ph...>
Date: Thu Jun 30 21:04:19 2016 +0300
Link to html'ized sources
[skip ci]
diff --git a/docs/DeveloperGuide.txt b/docs/DeveloperGuide.txt
index 3362c11..eca0491 100644
--- a/docs/DeveloperGuide.txt
+++ b/docs/DeveloperGuide.txt
@@ -38,30 +38,38 @@ Architecture
There are four main kinds of objects in SQLObject: tables, columns,
connections and converters.
-Tables-related objects are in sqlobject/main.py module. There are two
+Tables-related objects are in `sqlobject/main.py`_ module. There are two
main classes: SQLObject and sqlmeta; the latter is not a metaclass but a
parent class for sqlmeta attribute in every class - the authors tried to
move there all attributes and methods not directly related to columns to
avoid cluttering table namespace.
-Columns are instances of classes from sqlobject/col.py. There are two
+.. _`sqlobject/main.py`: sqlobject/main.py.html
+
+Columns are instances of classes from `sqlobject/col.py`_. There are two
classes for every column: one is for user to include into an instance of
SQLObject, an instance of the other is automatically created by
SQLObject metaclass. The two classes are names SOCol and Col; for
example, SOBoolCol and BoolCol.
+.. _`sqlobject/col.py`: sqlobject/col.py.html
+
Connections are instances of DBConnection class (from
-sqlobject/dbconnection.py ) and its concrete descendants. DBConnection
+`sqlobject/dbconnection.py`_) and its concrete descendants. DBConnection
contains generic code for generating SQL, working with transactions and
so on. Concrete connection classes (like PostgresConnection and
SQLiteConnection) provides backend-specific functionality.
-Converters from sqlobject/converters.py aren't visible to the user. They
+.. _`sqlobject/dbconnection.py`: sqlobject/dbconnection.py.html
+
+Converters from `sqlobject/converters.py`_ aren't visible to the user. They
are used behind the scene to convert object to SQL strings. The most
elaborated converter there is StringConverters. Yes, it converts strings
to strings. It converts python strings to SQL strings using
backend-specific quoting rules.
+.. _`sqlobject/converters.py`: sqlobject/converters.py.html
+
Style Guide
===========
http://sourceforge.net/p/sqlobject/sqlobject/ci/b85b7c37b1c12a727c5c16cef0564dd32a558abb
commit b85b7c37b1c12a727c5c16cef0564dd32a558abb
Author: Oleg Broytman <ph...@ph...>
Date: Thu Jun 30 20:40:36 2016 +0300
We, the developers...
[skip ci]
diff --git a/docs/DeveloperGuide.txt b/docs/DeveloperGuide.txt
index 3a04b21..3362c11 100644
--- a/docs/DeveloperGuide.txt
+++ b/docs/DeveloperGuide.txt
@@ -78,7 +78,7 @@ Python Style Guide. Some things to take particular note of:
* **No tabs**. Not anywhere. Always indent with 4 spaces.
-* I don't stress too much on line length. But try to break lines up
+* We don't stress too much on line length. But try to break lines up
by grouping with parenthesis instead of with backslashes (if you
can). Do asserts like::
@@ -98,7 +98,7 @@ Python Style Guide. Some things to take particular note of:
sqlobject import *`` so names should be fairly distinct, or they
shouldn't be exported in ``sqlobject.__init__``.
-* I'm very picky about whitespace. There's one and only one right way
+* We're very picky about whitespace. There's one and only one right way
to do it. Good examples::
short = 3
@@ -122,9 +122,9 @@ Python Style Guide. Some things to take particular note of:
func( a, b )
[ 1, 2, 3 ]
- To me, the poor use of whitespace seems lazy. I'll think less of
- your code (justified or not) for this very trivial reason. I will
- fix all your code for you if you don't do it yourself, because I
+ To us, the poor use of whitespace seems lazy. We'll think less of
+ your code (justified or not) for this very trivial reason. We will
+ fix all your code for you if you don't do it yourself, because we
can't bear to look at sloppy whitespace.
* Use ``@@`` to mark something that is suboptimal, or where you have a
@@ -210,8 +210,8 @@ miscellaneous functions.
.. _raises: http://pytest.org/latest/assert.html#assertions-about-expected-exceptions
-If you submit a patch or implement a feature without a test, I'll be
-forced to write the test. That's no fun for me, to just be writing
+If you submit a patch or implement a feature without a test, we'll be
+forced to write the test. That's no fun for us, to just be writing
tests. So please, write tests; everything at least needs to be
exercised, even if the tests are absolutely complete.
-----------------------------------------------------------------------
Summary of changes:
docs/DeveloperGuide.txt | 30 +++++++++++++++++++-----------
1 files changed, 19 insertions(+), 11 deletions(-)
hooks/post-receive
--
SQLObject development repository
|
