Upgrade pip to a particular version during local test and CI. #175

witten · 2019-05-14T17:30:38Z

witten commented

2019-05-14 17:30:38 +00:00

Attempt to work-around the work-around from witten/borgmatic#165 that appears to only support newer versions of pip.. by upgrading pip.

@decentral1se

Attempt to work-around the work-around from https://projects.torsion.org/witten/borgmatic/pulls/165 that appears to only support newer versions of pip.. by upgrading pip. @decentral1se

decentral1se commented

2019-05-14 18:48:45 +00:00

Ouch. Did you also try the following options:

Maybe we can specify the required Pip in the Tox configuration and also further isolate the build. If this works, I think it might be a nice solution. I just sat down to try and reproduce the error in witten/borgmatic#165 and I can't, which is weird.

Here's another disastrous hack for this packaging issue:

https://github.com/ansible/molecule/blob/master/tox.ini#L18

;)

Ouch. Did you also try the following options: * https://tox.readthedocs.io/en/latest/config.html#conf-requires * https://tox.readthedocs.io/en/latest/config.html#conf-isolated_build Maybe we can specify the required Pip in the Tox configuration and also further isolate the build. If this works, I think it might be a nice solution. I just sat down to try and reproduce the error in https://projects.torsion.org/witten/borgmatic/pulls/165 and I can't, which is weird. Here's another disastrous hack for this packaging issue: > https://github.com/ansible/molecule/blob/master/tox.ini#L18 ;)

decentral1se commented

2019-05-14 18:57:03 +00:00

FYI http://packaging.python.org/ 🔥 🔥 🔥

FYI http://packaging.python.org/ :fire: :fire: :fire:

witten commented

2019-05-14 18:59:03 +00:00

Just played around with both requires and isolated_build. No luck; same error.

Just played around with both `requires` and `isolated_build`. No luck; same error.

decentral1se approved these changes 2019-05-14 19:16:37 +00:00

decentral1se left a comment

Bombs away!