1. 27 Oct, 2016 3 commits
  2. 25 Oct, 2016 5 commits
  3. 10 Jun, 2016 10 commits
  4. 07 Jun, 2016 3 commits
  5. 06 Jun, 2016 1 commit
  6. 06 Apr, 2016 6 commits
  7. 16 Nov, 2015 3 commits
  8. 13 Nov, 2015 9 commits
    • Reinout van Rees's avatar
      Added python 3.5 build support · caff88e3
      Reinout van Rees authored
      caff88e3
    • Reinout van Rees's avatar
      Dropped python 3.2 as setuptools prints deprecation warnings · a4476cad
      Reinout van Rees authored
      The tests fail to run due to the deprecation warnings, so I stripped 3.2 out of travis.
      
      Added 3.5 instead as that's the most modern version.
      a4476cad
    • Reinout van Rees's avatar
      Updated changelog · 13d94d86
      Reinout van Rees authored
      13d94d86
    • Reinout van Rees's avatar
      Capitalization · 74eb44fb
      Reinout van Rees authored
      74eb44fb
    • Reinout van Rees's avatar
      1f623c0d
    • Reinout van Rees's avatar
      Using a different item for a package name · 0333f4d4
      Reinout van Rees authored
      "dist" can be a PathMetaData instance, req.key is nicer. The latter has a .lower()...
      0333f4d4
    • Reinout van Rees's avatar
      Adjusted test output to code change · 13e41011
      Reinout van Rees authored
      13e41011
    • Reinout van Rees's avatar
      Recording where requirements come from to debug version conflicts · d0a7f1bf
      Reinout van Rees authored
      Before you'd get a simple output like:
      
          Installing django.
          While:
            Installing django.
          Error: The requirement ('Django>=1.7') is not allowed by your [versions] constraint (1.6.6)
      
      ... which would mean you'd have to grep in all your requirements'
      sub-requirements which package actually requires the offending "django>=1.7"
      
      With this change you'll get a much more helpful output right before the error:
      
          Installing django.
          version and requirements information containing django:
            [versions] constraint on django: 1.6.6
            Base installation request: 'sso', 'djangorecipe'
            Requirement of djangorecipe==1.10: Django
            Requirement of djangorecipe==1.10: zc.recipe.egg
            Requirement of djangorecipe==1.10: zc.buildout
            Requirement of sso: django-nose
            Requirement of sso: django-mama-cas
            Requirement of sso: django-debug-toolbar
            Requirement of sso: django-auth-ldap
            Requirement of sso: Django<1.7,>=1.4.2
            Requirement of lizard-auth-server: django-nose
            Requirement of lizard-auth-server: django-extensions
            Requirement of lizard-auth-server: Django<1.7,>=1.6
            Requirement of django-nose: Django>=1.2
            Requirement of django-nose: nose>=1.2.1
            Requirement of django-mama-cas: requests==1.1.0
            Requirement of django-debug-toolbar: sqlparse
            Requirement of django-debug-toolbar: Django>=1.7
            Requirement of django-auth-ldap: python-ldap>=2.0
            Requirement of django-auth-ldap: django>=1.1
            Requirement of translations: Django>=1.4
            Requirement of django-extensions: six>=1.2
          While:
            Installing django.
          Error: The requirement ('Django>=1.7') is not allowed by your [versions] constraint (1.6.6)
      
      This makes it much easier to spot the cause (in this case
      django-debug-toolbar).
      
      There *are* some unrelated packages in here because I'm doing a textual
      comparison. The advantage is that it is very robust. And extracting the right
      package name from requirements without messing things up is harder to get
      right and takes more code.
      d0a7f1bf
    • Reinout van Rees's avatar
      Adjusted doctest to code change · 99202210
      Reinout van Rees authored
      - Adjusted the now-clearer error.
      - Removed error log message as that's now in the actual error message
      99202210