1. 13 Mar, 2017 1 commit
  2. 02 Mar, 2017 1 commit
    • Add support for using Pipeline CSS/JS packages in forms and widgets. (#620) · 67fef665
      Django allows forms and widgets to define the CSS or JavaScript files
      needed on the page, automatically including those files in the
      administration UI. This works fine for standalone media files, but
      weren't an option for Pipeline packages.
      
      This change introduces a branch new `PipelineFormMedia` class that a
      form or widget's Media class can inherit from. The Media class can then
      define `css_packages` or `js_packages` attributes that work just like
      the standard `css`/`js` attributes but reference package names instead
      of individual files.
      
      Upon accessing the `css`  or `js` attributes, the files defined in the
      packages will be collected/processed just like with the template tags
      and the resulting filenames returned for use in the page.
      
      Using this, any page compatible with Django's form media support will
      work automatically with any form or widget that wants to use Pipeline
      packages, without any modifications to templates or any other
      workarounds that were needed before.
      
      This implements issue #154.
      Christian Hammond committed
  3. 15 Jan, 2017 2 commits
  4. 31 Dec, 2016 1 commit
    • Fix a regression in determining when to collect static files. · d79be259
      A commit made in 1.6.10 (ae6b3f8e)
      changed a storage lookup to use the prefixed_path variable instead of
      the path variable when looking up modification times in order to
      determine if an existing collected file should be deleted and
      re-collected. By using the wrong path variable, the storage lookups
      always failed, resulting in every single file being re-collected every
      single time.
      
      This reduces performance considerably, particularly with large codebases.
      Since every file ends up copied, they appear as new and are recompiled.
      This can result in very long page reloads on a development server,
      especially if working on an older machine, in a VM, on a shared
      filesystem, or on the Linux subsystem for Windows.
      
      This is a simple change that fixes the lookup to use the correct
      variable. Unit tests were added to ensure this continues to work as
      expected and does not regress.
      Christian Hammond committed
  5. 17 Dec, 2016 1 commit
  6. 10 Nov, 2016 2 commits
  7. 27 Oct, 2016 1 commit
  8. 26 Oct, 2016 2 commits
  9. 20 Oct, 2016 6 commits
  10. 01 Sep, 2016 1 commit
  11. 30 Aug, 2016 3 commits
  12. 29 Aug, 2016 1 commit
  13. 26 Aug, 2016 1 commit
  14. 05 Jul, 2016 1 commit
  15. 01 Jul, 2016 1 commit
    • Added missing classifiers to the `setup.py` · aef2c094
      I have added extra topics:
      
      ```
      +        'Topic :: Software Development :: Libraries :: Python Modules',
      +        'Topic :: Internet :: WWW/HTTP',
      +        'Topic :: Internet :: WWW/HTTP :: Dynamic Content',
      ```
      
      Added information about framework:
      
      ```
      'Framework :: Django',
      'Framework :: Django :: 1.6',
      'Framework :: Django :: 1.7',
      'Framework :: Django :: 1.8',
      'Framework :: Django :: 1.9',
      ```
      
      And `python` versions:
      
      ```
              'Programming Language :: Python :: 2.7',
              ...
              'Programming Language :: Python :: 3.4',
              'Programming Language :: Python :: 3.5',
              'Programming Language :: Python :: Implementation :: PyPy',
      ```
      
      I have also sorted the classifiers alphabetically.
      Sobolev Nikita committed
  16. 11 Jun, 2016 2 commits
  17. 07 Jun, 2016 1 commit
  18. 28 May, 2016 1 commit
  19. 08 May, 2016 1 commit
  20. 31 Mar, 2016 3 commits
  21. 30 Mar, 2016 1 commit
  22. 29 Mar, 2016 2 commits
  23. 23 Mar, 2016 1 commit
    • Switch to using os.path for outdated file checks in compilers. · 930b12c9
      The outdated file checks in the compilers were using django storages to check
      file existence and compare mtimes, but with my recent change (which restored
      the older behavior of comparing the infile and outfile), these were operating
      on absolute, local files, which could result in a SuspiciousFileOperation.
      
      The compilers always operate on local files, so we can switch to using the
      os.path methods for these instead. This is both more correct and more
      efficient.
      David Trowbridge committed
  24. 22 Mar, 2016 2 commits
  25. 21 Mar, 2016 1 commit