Skip to content

Introduced pipfile #376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 14, 2019
Merged

Introduced pipfile #376

merged 4 commits into from
May 14, 2019

Conversation

ki4070ma
Copy link
Collaborator

For #365

ki4070ma added 3 commits May 8, 2019 00:16
Just created by pipenv install -r ci-requirements.txt
@mykola-mokhnach
Copy link
Contributor

Thanks Mori

Pipfile Outdated

[packages]
selenium = "==3.141.0"
astroid = "==1.6.5"
Copy link
Contributor

Choose a reason for hiding this comment

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

should we differentiate its version based on py3/py2?

Copy link
Member

Choose a reason for hiding this comment

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

No, 1.6.5 is enough I think.
astroid is used by pylint. Pylint 1.9.3 is necessary to run it for both versions.
Once we drop Python 2.7, we can remove this deps and update the pylint, too.

Copy link
Contributor

Choose a reason for hiding this comment

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

Then it makes sense to keep a TODO comment there

@@ -0,0 +1,19 @@
[[source]]
Copy link
Contributor

Choose a reason for hiding this comment

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

we can also explicitly point out which python versions are supported here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

You mean [requires] section?

If so, I removed from below description.
If no and you have example, it would be helpful.

https://docs.pipenv.org/en/latest/basics/#general-recommendations-version-control

Specify your target Python version in your Pipfile’s [requires] section. Ideally, you should only have one target Python version, as this is a deployment tool.

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah, sad but true: pypa/pipenv#1050

Pipfile Outdated
httpretty = "==0.9.6"
pytest = "==4.0.2"
pytest-cov = "==2.6.0"
tox = "==3.6.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

I would say it is fine to use any minor version above this rather than equal to

tox = "~=3.6"
tox-travis = "~=0.11"

# TODO Update to the latest ver when py2 support dropped
Copy link
Member

Choose a reason for hiding this comment

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

thanks

Copy link
Contributor

Choose a reason for hiding this comment

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

I mean you could do something like unittest2 = {version = ">=1.0,<3.0", markers="python_version < '2.7.9' or (python_version >= '3.0' and python_version < '3.4')"}

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, but at least for pylint/astroid/isort, point is #362 (comment) .

And as for other packages, same package versions are available for both py2 and py3.

@ki4070ma ki4070ma merged commit 6f6b26d into appium:master May 14, 2019
@ki4070ma ki4070ma deleted the pipfile branch May 14, 2019 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants