Closed
Bug 656508
Opened 15 years ago
Closed 13 years ago
multiple imports of jsobjects for no reason
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: k0scist, Assigned: berkerpeksag)
Details
(Whiteboard: [mentor=whimboo][lang=py][good first bug])
Attachments
(1 file)
|
940 bytes,
patch
|
whimboo
:
review+
|
Details | Diff | Splinter Review |
https://github.com/mozautomation/mozmill/blob/master/jsbridge/jsbridge/network.py#L103
jsobjects is imported twice. WHY? After the first import, there is
no additional action nor a separate namespacing (it is
module-global). It is looked up in sys.modules after the first
import.
Comment 1•14 years ago
|
||
Updated location is:
https://github.com/mozilla/mozmill/blob/master/jsbridge/jsbridge/network.py#L72
We should also move this to the top of the file.
Whiteboard: [mentor=whimboo][lang=py][good first bug]
| Assignee | ||
Comment 2•13 years ago
|
||
I've opened a pull request for this bug:
https://github.com/mozilla/mozmill/pull/113
Assignee: nobody → berker.peksag
Comment 3•13 years ago
|
||
Berker, thanks for your interest in working on that bug. Would you mind to attach a patch here instead of opening pull requests? We would appreciate that. Thanks.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•13 years ago
|
||
Attachment #700654 -
Flags: review?(hskupin)
Comment 5•13 years ago
|
||
Comment on attachment 700654 [details] [diff] [review]
Remove duplicate import of "jsobjects" module.
Review of attachment 700654 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good. I will get it checked-in in a moment. Thanks a lot even it was a trivial one. If you want to help with another bug feel free to look out for one or come back to me.
Attachment #700654 -
Flags: review?(hskupin) → review+
Comment 6•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•