Just a test

[tim-one]

BPO	400622
Nosy	@tim-one, @loewis
Files	None: None

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields: ```python assignee = 'https://github.com/tim-one' closed_at = created_at = labels = [] title = 'Just a test' updated_at = user = 'https://github.com/tim-one' ``` bugs.python.org fields: ```python activity = actor = 'loewis' assignee = 'tim.peters' closed = True closed_date = None closer = None components = ['None'] creation = creator = 'tim.peters' dependencies = [] files = ['2463'] hgrepos = [] issue_num = 400622 keywords = ['patch'] message_count = 10.0 messages = ['32822', '32823', '32824', '32825', '32826', '32827', '32828', '32829', '32830', '61833'] nosy_count = 2.0 nosy_names = ['tim.peters', 'loewis'] pr_nums = [] priority = 'normal' resolution = None stage = None status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue400622' versions = [] ```

[tim-one]

[tim-one]

Huh. Lotsa clicking needed to submit a patch via the web interface.

[tim-one]

So what does a second comment look like? First one took several minutes to complete after hitting "Submit Changes". Also, let's see whether structure is preserved in comments: if this is indented: hope this is indented more

[tim-one]

Bummer -- indentation is lost. Let's stick a blank line next:

Actually stuck two there.

[tim-one]

So \<bold>blank lines\</bold> do show up. Response time varies from seconds to minutes, & unrelated to the amount of text typed into the "add a comment" box. Changing status to "Postponed" for the heck of it.

[tim-one]

At least under IE5, right-clicking on "View Raw Patch" and selecting "Save Target As ..." manages to download the patch directly to a file, although it suggests the less than useful filename "download.php" by default.

[tim-one]

Man, that last one took so long I stopped the browser and hit "Submit Changes" again. Only one copy of the comment showed up, which is good.

Nice: SF is generated email to me each time the patch is updated. Unfortunately, I *suspect* this email goes only to the submittor, not also to the "assigned to" person. Check that later.

What else ... mysterious "close_date" records showing up in the Patch Change History.

[tim-one]

Man, that last one took so long I stopped the browser and hit "Submit Changes" again. Only one copy of the comment showed up, which is good.

Nice: SF is generated email to me each time the patch is updated. Unfortunately, I *suspect* this email goes only to the submittor, not also to the "assigned to" person. Check that later.

What else ... mysterious "close_date" records showing up in the Patch Change History.

[tim-one]

OK, not so good: the last comment did show up twice. Marking deleted.

[61337411-43fc-4a9c-b8d5-4060aede66d0]

This message links to msg32826