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

need setuptools >= 28.8.0 for PEP440 #470

Closed
wants to merge 1 commit into from

Conversation

meejah
Copy link
Contributor

@meejah meejah commented Mar 12, 2018

No description provided.

@codecov-io
Copy link

codecov-io commented Mar 12, 2018

Codecov Report

Merging #470 into master will decrease coverage by 2.88%.
The diff coverage is 97.01%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #470      +/-   ##
==========================================
- Coverage   93.03%   90.15%   -2.89%     
==========================================
  Files         232      144      -88     
  Lines       58668    27344   -31324     
  Branches     7649     3929    -3720     
==========================================
- Hits        54581    24651   -29930     
+ Misses       3122     1951    -1171     
+ Partials      965      742     -223
Impacted Files Coverage Δ
src/allmydata/scripts/cli.py 97.3% <ø> (ø) ⬆️
src/allmydata/web/magic_folder.py 100% <100%> (+22.22%) ⬆️
src/allmydata/frontends/magic_folder.py 87.18% <100%> (+1.3%) ⬆️
src/allmydata/node.py 93.22% <100%> (+0.1%) ⬆️
src/allmydata/client.py 87.13% <100%> (+0.03%) ⬆️
src/allmydata/scripts/tahoe_add_alias.py 79.04% <100%> (+9.15%) ⬆️
src/allmydata/scripts/create_node.py 98.32% <50%> (-0.66%) ⬇️
src/allmydata/immutable/upload.py 95.25% <0%> (-0.28%) ⬇️
src/allmydata/test/cli/test_put.py
src/allmydata/test/test_introducer.py
... and 85 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8f747c...e206f9f. Read the comment docs.

@meejah meejah force-pushed the fix-lgtm branch 4 times, most recently from e41ef6e to d003de4 Compare March 13, 2018 02:02
(needs fixup, probably, just depending on latest setuptools)
@tpltnt
Copy link
Contributor

tpltnt commented Mar 13, 2018

looks good to me

@warner warner changed the title need setuptools >= 8.0 for PEP440 need setuptools >= 28.8.0 for PEP440 Mar 14, 2018
@warner
Copy link
Member

warner commented Mar 20, 2018

I'm going to land this, and see if it helps the LGTM baseline build. I'm not sure that 28.8.0 is strictly necessary (I think the "python_version <=.." clause in zfec's setup.py might be an "environment marker", in which case 20.8.1 is probably sufficient, but OTOH our python_requires="<3.0" line requires 24.2.1), but it ought to fix the problem, and it isn't as severe a constraint on packagers as requiring the most recent version (39.0.1).

@warner warner closed this in 7960a1b Mar 20, 2018
@warner
Copy link
Member

warner commented Mar 20, 2018

although, note that the travis problem was with the "tox -e codechecks" build. I wonder if we need to explicitly upgrade setuptools in the tox config. The error only happened on the OS-X builder, and maybe it has an older version pre-installed.

@exarkun
Copy link
Member

exarkun commented Mar 20, 2018

Reverted in 3bb4c97 because the change reliably breaks the OS X builder.

@exarkun exarkun reopened this Mar 20, 2018
warner added a commit to warner/tahoe-lafs that referenced this pull request Mar 21, 2018
The Travis OS-X worker has a very old setuptools-18.5 in /System. This is too
old to understand several important setup.py keys like `python_requires`, and
crashes when tryung to run the first invocation of tox (`tox -e codechecks`).
I think tox is using the system python (with which `tox` was invoked) to run
`setup.py egg_info` (to learn the dependencies), which gets the old
system-installed setuptools. Ideally it'd use the python from the
newly-created virtualenv, which would use whatever version of setuptools was
bundled with the `virtualenv` package (probably newer, given that
`virtualenv` itself should have been installed a moment earlier as a
dependency of `tox`.

I consider this a bug in Tox (tox-dev/tox#507), but
the workaround is to configure Travis to install the most recent `setuptools`
along with `tox`.

refs tahoe-lafs#470
@warner warner closed this in 57066b0 Mar 21, 2018
@warner
Copy link
Member

warner commented Mar 21, 2018

replaced by #473

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants