Please import these Pyflakes tickets
Per <https:/
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- William Grant Edit question
- Last query:
- 2011-03-20
- Last reply:
- 2011-04-08
- Whiteboard:
- The import was done on staging, but erased before it could be checked. Need to rerun.
Jean-Paul Calderone (exarkun) said : | #1 |
I guess there's no way to attach a file to a question, so here's the dump: http://
j.c.sackett (jcsackett) said : | #2 |
I have run an import in a local instance and everything looks good--no bugs encountered any data problems, and everything looks reasonable. I did set the data so that bugs will have nick of pyflakes-
I have requested a losa to run the import into pyflakes on staging.
When that is done, I will post here asking you to review the data. I see that you are the maintainer for PyFlakes on lp; you will have to set the bugtracker to launchpad in order to see the and review the bug data.
j.c.sackett (jcsackett) said : | #3 |
This has been imported into staging. As I said before, you will need to set pyflakes to use launchpad for bugtracking to be able to see the bugs.
William Grant (wgrant) said : | #4 |
We've reimported it on qastaging, where it's less likely to be erased before you can see it. As before, visit https:/
Can you help with this problem?
Provide an answer of your own, or ask Jean-Paul Calderone for more information if necessary.