Skip to content
Permalink
Browse files

Reviewed deps

  • Loading branch information...
lasote committed Oct 19, 2018
1 parent ab45954 commit f290f8025c2e34bad89bc80effaafa4954e303b8
Showing with 2 additions and 4 deletions.
  1. +1 −1 conans/__init__.py
  2. +1 −1 conans/requirements.txt
  3. +0 −2 conans/requirements_osx.txt
@@ -18,5 +18,5 @@
REVISIONS = "revisions" # Only when enabled in config, not by default look at server_launcher.py
SERVER_CAPABILITIES = [COMPLEX_SEARCH_CAPABILITY, ] # Still without v2 because it is changing

__version__ = '1.8.3'
__version__ = '1.8.4'

@@ -12,4 +12,4 @@ future==0.16.0
pygments>=2.0, <3.0
astroid>=1.6.5
deprecation>=2.0, <2.1
tqdm==4.20.0

This comment has been minimized.

Copy link
@tivek

tivek Oct 19, 2018

Contributor

What is the reason to fork tqdm 4.27.0?

This comment has been minimized.

Copy link
@memsharded

memsharded Oct 19, 2018

Contributor

Because it is very problematic to install, as it tries to install to the "man" folder, which is non-existing and fails. The issue is reported upstream to tqdm, but will take a while to be released, it seems. Meanwhile, it seems that the least problematic way to install Conan is with this fork. Is there any problem for you (ArchLinux)?

This comment has been minimized.

Copy link
@tivek

tivek Oct 19, 2018

Contributor

I see. I'm relying on the python-tqdm package from Arch repos. They seem to have worked around the man issue back in tqdm 4.19.1, so until now I was unaware there even was a problem..

tqdm-conan==4.27.0
@@ -1,5 +1,3 @@
idna==2.6 # Solving conflict, somehow is installing 2.7 when requests require 2.6
cryptography>=1.3.4, <2.4.0
pyOpenSSL>=16.0.0, <18.0.0
ndg-httpsclient>=0.4.1, <0.5.0
pyasn>=1.5.0b7, <1.6.0

0 comments on commit f290f80

Please sign in to comment.
You can’t perform that action at this time.