A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133421.html below:

assert[Raises|Warns]Regex now raise TypeError on bad regex.

[Python-Dev] cpython: #20145: assert[Raises|Warns]Regex now raise TypeError on bad regex. [Python-Dev] cpython: #20145: assert[Raises|Warns]Regex now raise TypeError on bad regex.R. David Murray rdmurray at bitdance.com
Mon Mar 24 00:44:42 CET 2014
On Sun, 23 Mar 2014 21:43:14 +0100, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Sun, 23 Mar 2014 20:47:28 +0100 (CET)
> r.david.murray <python-checkins at python.org> wrote:
> > http://hg.python.org/cpython/rev/ec556e45641a
> > changeset:   89936:ec556e45641a
> > user:        R David Murray <rdmurray at bitdance.com>
> > date:        Sun Mar 23 15:08:43 2014 -0400
> > summary:
> >   #20145: assert[Raises|Warns]Regex now raise TypeError on bad regex.
> > 
> > Previously a non-string, non-regex second argument could cause the test
> > to always pass.
> 
> It seems like this would be useful to fix in 3.4 too.

You will note that the change got a porting note in What's New.  It will
only break tests (that are currently no-ops), not code, so I'd be fine
with backporting it, but the original issue did not call for that.

If we fix it in 3.4, should we fix it in 2.7 as well?

--David
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4