➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020-01-21 10:11:28 | cheryl.sabella | set | status: open -> merged |
| 2020-01-15 19:23:57 | cheryl.sabella | set | title: bpo-32989: IDLE - fix pyparse.find_good_parse_start and bad editor call -> bpo-32989: IDLE - fix bad editor call of pyparse method |
| 2018-12-29 05:12:55 | cheryl.sabella | set | title: bpo-35610: IDLE - fix pyparse.find_good_parse_start and bad editor call -> bpo-32989: IDLE - fix pyparse.find_good_parse_start and bad editor call |
| 2018-12-29 05:12:13 | cheryl.sabella | set | title: bpo-32989: IDLE - fix pyparse.find_good_parse_start and bad editor call -> bpo-35610: IDLE - fix pyparse.find_good_parse_start and bad editor call |
| 2018-03-04 08:35:37 | cheryl.sabella | set | title: bpo-32989: IDLE - fix pyparse.find_good_parse_start None bug and bad call -> bpo-32989: IDLE - fix pyparse.find_good_parse_start and bad editor call |
| 2018-03-04 08:29:00 | cheryl.sabella | set | title: bpo-32989: IDLE: Correct call from editor to pyparse -> bpo-32989: IDLE - fix pyparse.find_good_parse_start None bug and bad call |
| 2018-03-03 23:39:13 | cheryl.sabella | link | issue32989 pull_requests |
| 2018-03-03 23:39:13 | cheryl.sabella | create | |