1. 07 Jul, 2014 4 commits
  2. 03 Jul, 2014 1 commit
  3. 02 Jul, 2014 4 commits
  4. 19 Jun, 2014 2 commits
  5. 18 Jun, 2014 1 commit
    • Hugo Rodger-Brown's avatar
      Update pylibmc to support nested requirements. · 826193ef
      Hugo Rodger-Brown authored
      The current regex assumes that pylibmc appears at the beginning of a line
      (whitespace only precedes it), which is a fair assumption in a single 'flat'
      requirements.txt file. However, if you are using nested requirements then
      this is not the case - your pylibmc may exist in a sub-directory. This is
      very similar to the way in which mercurial is installed if "hg+" is found
      in the requirements file (see the /bin/compile script). By insisting that
      pylibmc appear at the beginning of the file, it's impossible to fool the
      compilation into installing libmemcached (as this script does) by simply
      putting the phrase into a comment, which is what you *can* do with 'hg+'.
      I've updated the regex to remove the beginning of line restriction. This
      means that you can add a comment to a top-level requirements.txt that
      will trigger the install, without having to functionally alter your
      nested requirements.
      e.g. top-level requirements.txt:
          # fake comment to trigger pylibmc script
          # fake comment to trigger hg+ install
          -r requirements/production.txt
  6. 17 Jun, 2014 1 commit
  7. 12 Jun, 2014 1 commit
  8. 04 Jun, 2014 3 commits
  9. 03 Jun, 2014 4 commits
  10. 02 Jun, 2014 19 commits