<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/paste-git.git/paste/exceptions, branch benjaminp-fixture-unicode-paths</title>
<subtitle>github.com: cdent/paste.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/paste-git.git/'/>
<entry>
<title>Remove use of future</title>
<updated>2018-10-24T21:46:20+00:00</updated>
<author>
<name>Chris Dent</name>
<email>cdent@anticdent.org</email>
</author>
<published>2018-10-24T21:46:20+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/paste-git.git/commit/?id=00f4fde04bdd841ec88c2b62dd9dcab92a3d019d'/>
<id>00f4fde04bdd841ec88c2b62dd9dcab92a3d019d</id>
<content type='text'>
Future is calling installation endless recursion. We are only
using it for an html.escape method, so we make our own and get
rid of future.

Related-Bug: #6
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Future is calling installation endless recursion. We are only
using it for an html.escape method, so we make our own and get
rid of future.

Related-Bug: #6
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix up testing after switch to pytest</title>
<updated>2018-10-23T16:01:47+00:00</updated>
<author>
<name>Chris Dent</name>
<email>cdent@anticdent.org</email>
</author>
<published>2018-10-23T16:01:47+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/paste-git.git/commit/?id=9fcc98bd3e5bde3a26326f3156845093f84b8832'/>
<id>9fcc98bd3e5bde3a26326f3156845093f84b8832</id>
<content type='text'>
pytest exposes many warnings, some but not all of which are cleaned
up here. The main switch is to use html.escape instead of cgi.escape.
This inspired the addition of 'future' to requirements.

The remaining warnings are related to pytest deprecations or over-eager
test discovery.

It is perhaps ironic that the switch to pytest is to avoid nose being
mostly dead, and now we are using features in pytest that pytest wants
to make dead. These are left for later cleanups, which means that
running the tests is noisy.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
pytest exposes many warnings, some but not all of which are cleaned
up here. The main switch is to use html.escape instead of cgi.escape.
This inspired the addition of 'future' to requirements.

The remaining warnings are related to pytest deprecations or over-eager
test discovery.

It is perhaps ironic that the switch to pytest is to avoid nose being
mostly dead, and now we are using features in pytest that pytest wants
to make dead. These are left for later cleanups, which means that
running the tests is noisy.
</pre>
</div>
</content>
</entry>
<entry>
<title>Don't raise StopIteration from generator, return instead</title>
<updated>2018-06-08T16:49:42+00:00</updated>
<author>
<name>Miro Hron?ok</name>
<email>miro@hroncok.cz</email>
</author>
<published>2018-06-08T16:49:42+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/python-packages/paste-git.git/commit/?id=bb9bdf7e5b5cb0d3458242c5b8ba6134efb282a4'/>
<id>bb9bdf7e5b5cb0d3458242c5b8ba6134efb282a4</id>
<content type='text'>
See https://www.python.org/dev/peps/pep-0479/
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
See https://www.python.org/dev/peps/pep-0479/
</pre>
</div>
</content>
</entry>
</feed>
