Bug#597120: [PATCH] Avoid dumping unparseable data

John Wright jsw at debian.org
Wed Sep 22 05:36:55 UTC 2010


On Mon, Sep 20, 2010 at 10:37:08AM -0700, Jelmer Vernooij wrote:
> Hi John,
> 
> On Sat, 2010-09-18 at 02:15 -0600, John Wright wrote:
> > Add an input validation method that is called by the default __setitem__,
> > and add some validation at output time for multivalued fields (since
> > their input is a mutable list which makes it unsuitable for validation
> > at intput time).
> "Changes" in the changes file often contains empty lines, and I think we
> should keep being able to generate files like that.  I haven't actually
> tried but from reading your patch it looks like it would also refusing
> setting a field with empty lines even if it is the last one?

Really?  It could contain lines like ' .\n', but never just '\n'...  Any
tool creating a .changes file with truly empty lines is broken, and I'm
pretty sure deb822 would refuse to read any data after the first blank
line, anyway, with or without this patch.

-- 
John Wright <jsw at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-python-debian-maint/attachments/20100921/de9e174c/attachment.pgp>


More information about the pkg-python-debian-maint mailing list