Skip to content
This repository has been archived by the owner on Feb 28, 2022. It is now read-only.

Move lib #291

Merged
merged 3 commits into from
Feb 21, 2017
Merged

Move lib #291

merged 3 commits into from
Feb 21, 2017

Conversation

sachs7
Copy link
Contributor

@sachs7 sachs7 commented Feb 21, 2017

  • import library as per PEP8.

suplaonkar and others added 3 commits February 17, 2017 16:24
- Update to test_group.py to use UUID for unique name
- import library as per PEP8.
Copy link
Contributor

@stephendonner stephendonner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Carrying over r+ from earlier pull (290), and based on my own review + ad-hoc run:

https://gist.github.com/stephendonner/d9453de236f8104630df60e979479d04

@stephendonner
Copy link
Contributor

Thanks for the PR, @sachs7 - really great to have you contributing! Let us know if we can help in any way!

@sachs7
Copy link
Contributor Author

sachs7 commented Feb 21, 2017

Thanks, @stephendonner, it is my first PR to open source community. I will look at other open issues and try to fix some.

@stephendonner
Copy link
Contributor

Great; if you're interested, @sachs7 - would you mind going through http://firefox-test-engineering.readthedocs.io/en/latest/ and either filing Issues (https://github.com/mozilla/firefox-test-engineering/issues) or pull requests to fix anything obviously unclear/missing?

@sachs7
Copy link
Contributor Author

sachs7 commented Feb 21, 2017

@stephendonner going through the links which you shared above.


import pytest

from random import randrange

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was no need to move this line down. Both uuid and random are standard library modules, so according to PEP8 these should be grouped together. See https://www.python.org/dev/peps/pep-0008/#imports for more details.

@davehunt
Copy link
Member

Thanks @sachs7! So you know, there's no need to create new branches and open new pull requests after addressing review comments. You can simply add new commits to your existing branch and push it. GitHub will then update the open pull request with the new commits.

@sachs7
Copy link
Contributor Author

sachs7 commented Feb 22, 2017

Thanks, @davehunt. It was a good learning and I will improve on it. Thanks, for your suggestion and will keep it in mind.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants