User Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0 Build ID: 20121128204232 Steps to reproduce: I tried to work with the development version of Mozmill 2.0, but I got an error when I ran setup_development.py script. Actual results: The error stack is: Traceback (most recent call last): File "setup.py", line 22, in description = file(os.path.join(here, 'README.md')).read() NameError: name 'file' is not defined Traceback (most recent call last): File "setup.py", line 20, in description = file(os.path.join(here, 'README.md')).read() NameError: name 'file' is not defined Traceback (most recent call last): File "setup.py", line 19, in assert sys.version_info == 2 AssertionError Expected results: Everything should has worked fine, as if I had used Python 2.x.
This might be, yes. Version 3 is not on the support list for Mozmill yet. And not sure if we have the time to put man hours in that. If you want to help and make Mozmill 2.0 Python 3.0 compliant I'm happy to accept patches. But it will most likely not block version 2.0.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Latest Mozmill 2.0 doesn't work with Python 3 → Latest Mozmill doesn't work with Python 3
It would be good to know how Mozmill behaves with Python 3 those days. Putting this up as a mentored bug.
Whiteboard: [mentor=whimboo][lang=py] → [mentor=whimboo][lang=py][good first bug]
Hi, I would like to work on this bug. I'm new so I need some mentoring for start.
Hello Dubaj. It's great to see that you have interests in working on this bug, and learning more about Mozmill automation. I'm around to help you in whatever questions you have. Just let me know. For now I updated the URL field, so you get the instructions how to get started. In general you might want to install Python 2.7.x and the latest 3.x release. Once you got the Mutt tests running with 2.7.x, you can compare the results when those tests get run with 3.x. You might also want to join us on IRC in the #mozmill or #automation channel. I'm around for direct help there.
Assignee: nobody → dubaj.andrzej
Status: NEW → ASSIGNED
Ok thanks for the info. Could we meet up for the IRC on Sunday ?
I will not be around over the weekend. Maybe you want to send an email to get necessary information ahead of time.
Ok. Thank You for information. I send email to You and I wrote some questions. I'll be waiting for a response from You.
Dubaj, in the future feel free to ask those questions here in the bug directly. That way everyone working on Mozmill and its tests can help you. Regarding your email I replied it now. Good to see that you are working on this bug.
Whiteboard: [mentor=whimboo][lang=py][good first bug] → [lang=py][good first bug]
Dubaj, It has been almost 2 months, I want to make sure you haven't forgot about this bug as it is assigned to you. If you don't have time to work on it, please let us know and we can open it up for others to work on it.
Hello, yes I working on it. Sorry for a lack of communication from long time.
this is a hard problem to solve, no worries about it taking a while. Please feel free to ask questions if something doesn't make sense.
Ok. Thanks for information. I still working on this issue. I will probably need more information from the person reporting the bug.
Best here would be to create a virtualenv with python 3.x, install Mozmill, run all the mutt tests, and report all failures back here. We can then discuss them, and separate into own bugs.
Mozmill will reach its end of life soon. We are currently working on getting all the tests for Firefox ported to Marionette. For status updates please see bug 1080766.
Assignee: dubaj.andrzej → nobody
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
Whiteboard: [lang=py][good first bug]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.