TODO

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2007-08-08 10:24:59 →
Size: 1112
Editor: a89-182-21-236
Comment:
← Revision 2 as of 2007-08-08 15:46:25 → ⇥
Size: 1122
Editor: a89-182-21-236
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
The syntax of that function in combination with the `bug.attachments.filter()`-function looks strange: The syntax of that function in combination with the `bug.attachments.filter()`-function looks strange: (./)
Line 30: Line 30:
allow `duplicate_of = None` allow `duplicate_of = None` (./)

TODO

This is a list of known issues:

change bug.attachments.remove()

The syntax of that function in combination with the bug.attachments.filter()-function looks strange: (./) 

bug.attachments.remove([i for i in bug.attachments.filter(lambda a: re.match('^(CoreDump.gz$|Stacktrace.txt|ThreadStacktrace.txt|Dependencies.txt$|ProcMaps.txt$|ProcStatus.txt$|Registers.txt$|Disassembly.txt$)', a.lp_filename))])

relation between attachment and comment

Using weakref is not the best solution and it seems to be broken sometimes. Suggestion:

  • really delete an attachment
    • bug.comment[x].attachments should be a list of attachment-ids
    • add a 'deleted-attachment`-object:
      • whenever an attachment is deleted .comment.attachment[x] should refer to the deleted attachment
  • set attachment as deleted
    • add attachment.deleted attribute

    • bug.attachments will return list of attachments where .deleted== False

    • .comment.attachment[x] will return either an <dead-object> or raise an error

duplicate_of

allow duplicate_of = None (./)

BugHelper/Dev/python-launchpad-bugs/TODO (last edited 2008-08-06 16:14:38 by localhost)