Skip to content
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

Moved the metadata into setup.cfg #497

Merged
merged 1 commit into from Apr 2, 2020

Conversation

KOLANICH
Copy link
Contributor

@KOLANICH KOLANICH commented Feb 7, 2020

No description provided.

setup.cfg Outdated Show resolved Hide resolved
setup.py Outdated Show resolved Hide resolved
setup.py Outdated Show resolved Hide resolved
@coveralls
Copy link

coveralls commented Feb 12, 2020

Coverage Status

Coverage decreased (-0.04%) to 82.793% when pulling c060cb1 on KOLANICH:setup.cfg into 850693c on tomerfiliba:master.

@KOLANICH
Copy link
Contributor Author

KOLANICH commented Mar 1, 2020

Travis CI build has failed because psutil has dropped pypy 2.7. Taking in account that python 2.7 is EOL, should we drop pypy 2.7 too or should we just apply a patch removing the antifeature from psutil?

@henryiii
Copy link
Collaborator

henryiii commented Mar 6, 2020

I'll try to fix the CI soon. Note from that link: I'm just giving up on a specific broken PyPy2 version which hopefully will be fixed soon. - looks like PyPy 2 support is not gone yet, just partially broken. Note that Python 3 support has been much slower in PyPI, with 3 being called beta support until recently. PyPy 2.7 is still very common. Hopefully will start to die out though now that main Python 2 is going out.

Dropping PyPy 2.7 doesn't really bother me, honestly though. Plumbum needs to work out-of-the box on all systems, but no system has only PyPy (2.7).

pyproject.toml Outdated Show resolved Hide resolved
setup.py Outdated
},
platforms = ["POSIX", "Windows"],
provides = ["plumbum"],
keywords = "path, local, remote, ssh, shell, pipe, popen, process, execution, color, cli",
cmdclass = {'test':PyTest,
Copy link
Collaborator

@henryiii henryiii Mar 12, 2020

Choose a reason for hiding this comment

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

I'm okay with killing off 'test' and test_requires too, by the way (doesn't need to be in this PR); Python is deprecating setup.py test. The only correct way to run the tests is via pytest.

setup.cfg Outdated
plumbum.path
plumbum.fs
plumbum.colorlib
setup_requires = setuptools>=44; wheel; setuptools_scm[toml]>=3.4.3
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please remove this line. setup_requires is deprecated.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think we should remove it (older versions of setuptools that don't know about pyproject.toml should understand that).

But as you wish, it's not a very strong issue, ones staying on bleeding edge (like me) should not encounter any issues from that.

Copy link
Contributor Author

@KOLANICH KOLANICH Mar 12, 2020

Choose a reason for hiding this comment

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

It turned out without this line builds fail.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Okay. Should only affect building wheels, which only devs and CI does, but maybe we don’t have the CI up to date. It doesn’t hurt to have it.

@KOLANICH KOLANICH force-pushed the setup.cfg branch 6 times, most recently from da582bf to f05ed83 Compare March 12, 2020 22:04
@henryiii
Copy link
Collaborator

@KOLANICH, how about we merge #506 , then make a 1.6.9 release, then dump Python 2.6 for good and merge this as the beginning of 1.7.0?

@KOLANICH
Copy link
Contributor Author

KOLANICH commented Mar 13, 2020

Do what you feel is right. I am OK to wait until any next releases as long as it doesn't take long to wait. I mean not months and not years. IMHO it is OK to have 10 seconds between 2 releases :).

@KOLANICH KOLANICH force-pushed the setup.cfg branch 3 times, most recently from da56998 to fe4e96f Compare March 13, 2020 21:59
@henryiii
Copy link
Collaborator

1.6.9 is out. Feel free to drop 2.6!

@henryiii henryiii merged commit 6788d15 into tomerfiliba:master Apr 2, 2020
@henryiii
Copy link
Collaborator

henryiii commented Apr 2, 2020

Fantastic, thanks! Thanks also for cleaning out a few ugly 2.6 workarounds!

@henryiii henryiii added this to the v1.7.0 milestone Feb 8, 2021
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.

None yet

3 participants