• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

applegrew / django-select2 / 127 / 2
100%
master: 34%

Build:
Build:
LAST BUILD BRANCH: codingjoe-patch-1
DEFAULT BRANCH: master
Ran 19 Jul 2015 05:18PM UTC
Files 13
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

19 Jul 2015 05:16PM UTC coverage: 67.534% (+0.04%) from 67.49%
DJANGO="<1.8,>=1.7"

push

travis-ci

codingjoe
Removed own caching solution in favour of django caching

The old multiprocessing support was hard to maintain.
Since signing and caching are part of `django.core`
there is really no need to stick to our own solution.

As a result multimachine support and security are now always in place.
Fields are stored in Django's cache. The default cache used by select2
is called 'default' but can be cachanged overwriting the setting
`SELECT2_CACHE_BACKEND`.

Recommended cache backends are memcached, redis or a DB-cache.

Refactored AutoResponseView

The main reason for this refactoring is
the fact that the pagingnation was slow.

I dropped major parts of the initial code
and wrote a more django-like-approach.

Noteabley:
- get_results now retuns a QuerySet
- This commit drops django 1.6 support in favour of the JsonResponse (Backporting is possible).

493 of 730 relevant lines covered (67.53%)

0.68 hits per line

Source Files on job 127.2 (DJANGO="<1.8,>=1.7")
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 127
  • Travis Job 127.2
  • 2b20c252 on github
  • Prev Job for DJANGO="<1.8,>=1.7" on v5 (#126.2)
  • Next Job for DJANGO="<1.8,>=1.7" on v5 (#128.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc