You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
create a separate branch, push it to your fork and create a pull request
64
64
to the original repo. That way CI will be triggered to test your code.</p>
65
65
<p>Voila! The packages are globally installed, but the files from the
66
-
checkout were not copied into <ttclass="docutils literal"><spanclass="pre">site-packages</span></tt>. See <ahref="http://pythonhosted.org/setuptools/" class="reference external">setuptools</a> for more.</p>
66
+
checkout were not copied into <ttclass="docutils literal"><spanclass="pre">site-packages</span></tt>. See <ahref="https://setuptools.readthedocs.io/en/latest/index.html" class="reference external">setuptools</a> for more.</p>
67
67
</div>
68
68
<divclass="section" id="architecture">
69
69
<h1>Architecture</h1>
@@ -123,7 +123,7 @@ <h2>Columns, validators and converters</h2>
123
123
</div>
124
124
<divclass="section" id="style-guide">
125
125
<h1>Style Guide</h1>
126
-
<p>Generally you should follow the recommendations in <ahref="http://www.python.org/peps/pep-0008.html" class="reference external">PEP 8</a>, the
126
+
<p>Generally you should follow the recommendations in <ahref="http://www.python.org/dev/peps/pep-0008/" class="reference external">PEP 8</a>, the
127
127
Python Style Guide. Some things to take particular note of:</p>
128
128
<ulclass="simple">
129
129
<li>With a few exceptions sources must be <ahref="https://gitlab.com/pycqa/flake8" class="reference external">flake8</a>-clean (and hence
@@ -234,9 +234,9 @@ <h1>Style Guide</h1>
234
234
<h1>Testing</h1>
235
235
<p>Tests are important. Tests keep everything from falling apart. All
236
236
new additions should have tests.</p>
237
-
<p>Testing uses py.test, an alternative to <ttclass="docutils literal">unittest</tt>. It is available at
<p>Testing uses py.test, an alternative to <ttclass="docutils literal">unittest</tt>. It is available
238
+
at <ahref="http://pytest.org/" class="reference external">http://pytest.org/</a> and <ahref="https://pypi.python.org/pypi/pytest" class="reference external">https://pypi.python.org/pypi/pytest</a>. Read its
239
+
<ahref="http://docs.pytest.org/en/latest/getting-started.html" class="reference external">getting started</a> document for more.</p>
240
240
<p>To actually run the test, you have to give it a database to connect to.
241
241
You do so with the option <ttclass="docutils literal"><spanclass="pre">-D</span></tt>. You can either give a complete URI or
242
242
one of several shortcuts like <ttclass="docutils literal">mysql</tt> (these shortcuts are defined in
@@ -252,7 +252,7 @@ <h1>Testing</h1>
252
252
<p><ttclass="docutils literal">supports(featureName)</tt> checks if the database backend supports the
253
253
named feature. What backends support what is defined at the top of
254
254
<ttclass="docutils literal">dbtest</tt>.</p>
255
-
<p>If you <ttclass="docutils literal">import *</tt> you'll also get py.test's version of <ahref="http://pytest.org/latest/assert.html#assertions-about-expected-exceptions" class="reference external">raises</a>, an
255
+
<p>If you <ttclass="docutils literal">import *</tt> you'll also get py.test's version of <ahref="http://docs.pytest.org/en/latest/assert.html#assertions-about-expected-exceptions" class="reference external">raises</a>, an
256
256
<ttclass="docutils literal">inserts</tt> function that can create instances for you, and a couple
257
257
miscellaneous functions.</p>
258
258
<p>If you submit a patch or implement a feature without a test, we'll be
@@ -261,7 +261,7 @@ <h1>Testing</h1>
261
261
exercised, even if the tests are absolutely complete.</p>
262
262
<p>We now use Travis CI to run tests. See the status:</p>
<p>To avoid triggering unnecessary test run at Travis add text <ahref="https://docs.travis-ci.com/user/customizing-the-build/#Skipping-a-build" class="reference external">[ci skip]</a>
264
+
<p>To avoid triggering unnecessary test run at Travis add text <ahref="https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build" class="reference external">[ci skip]</a>
265
265
anywhere in your commit messages for commits that don't change code
Copy file name to clipboardExpand all lines: devel/Inheritance.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -198,9 +198,9 @@ <h2>Why</h2>
198
198
</div>
199
199
<divclass="section" id="who-what-and-how">
200
200
<h2>Who, What and How</h2>
201
-
<p>Daniel Savard has implemented inheritance for SQLObject. According to
202
-
<ahref="http://www.objectmatter.com/vbsf/docs/maptool/ormapping.html" class="reference external">ObjectMatter</a> this is a kind of vertical inheritance. The only difference
203
-
is that objects reference their leaves, not parents. Links to parents are
201
+
<p>Daniel Savard has implemented inheritance for SQLObject. In <ahref="https://cayenne.apache.org/docs/3.0/modeling-inheritance.html" class="reference external">terms of
202
+
ORM</a> this is a kind of vertical inheritance. The only difference is
203
+
that objects reference their leaves, not parents. Links to parents are
204
204
reconstructed at run-time using the hierarchy of Python classes.</p>
205
205
<ulclass="simple">
206
206
<li>As suggested by Ian Bicking, each child class now has the same
0 commit comments