On Sun, May 31, 2015 at 1:23 PM, Mads Kiilerich wrote:
> On 05/31/2015 12:57 PM, Thomas De Schampheleire wrote:
>>
>> Hi,
>>
>> I've been using pytest for a while now, and think we should consider
>> making it the default test suite instead of nose.
>>
>> As I see it, there are following points to
# HG changeset patch
# User Thomas De Schampheleire
# Date 1433073387 -7200
# Sun May 31 13:56:27 2015 +0200
# Node ID 19d7fb2450cf730a5bf5bc0c69a79c67c1cd
# Parent baedf806eb0be5eb3b5acb019319d57b8ba24c14
files: fix invalid links to Last Revision
The Last Revision column of the file br
v2: test and fix unicode handling
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
# HG changeset patch
# User Thomas De Schampheleire
# Date 1432065035 -7200
# Tue May 19 21:50:35 2015 +0200
# Node ID 20bf71e88042ca1f519c4ee711fa436564360755
# Parent 579110ca5178f13254e7e4c7b6043767a11b92a2
login: preserve GET arguments throughout login redirection (issue #104)
When redi
# HG changeset patch
# User Thomas De Schampheleire
# Date 1431287504 -7200
# Sun May 10 21:51:44 2015 +0200
# Node ID baedf806eb0be5eb3b5acb019319d57b8ba24c14
# Parent 2c1ae0b188ae5f5fde6369f76803a1170592b90d
pullrequest/compare: add logical changeset index to clarify the order
Is the pare
On 05/31/2015 12:57 PM, Thomas De Schampheleire wrote:
Hi,
I've been using pytest for a while now, and think we should consider
making it the default test suite instead of nose.
As I see it, there are following points to do:
1. silence the database setup code by default. Currently, the initial
Hi,
I've been using pytest for a while now, and think we should consider
making it the default test suite instead of nose.
As I see it, there are following points to do:
1. silence the database setup code by default. Currently, the initial
step of the tests sets up the database and all commands