pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2012-04-18	PLIST fix for pgsql	adam	1	-4/+16

2012-04-17	Changes 1.4:	adam	1	-205/+585
	* Support for time zones * Support for in-browser testing frameworks * Updated default project layout and manage.py * Custom project and app templates * Improved WSGI support * Improved password hashing * HTML5 doctype * List filters in admin interface * Multiple sort in admin interface * New ModelAdmin methods More...
2012-04-08	All supported python versions in pkgsrc support eggs, so remove	wiz	1	-2/+2
	${PLIST.eggfile} from PLISTs and support code from lang/python.
2012-01-26	distutils pkg, register egg-info.	obache	1	-1/+2
	Bump PKGREVISION.
2011-09-12	Changes 1.3.1:	adam	1	-2/+10
	Fixed security issues: * Session manipulation * Denial of service attack via URLField * URLField redirection * Host header cache poisoning * Advisory: Host header and CSRF * Advisory: Cross-subdomain CSRF attacks * Advisory: DEBUG pages and sensitive POST data
2011-03-23	Changes 1.3:	adam	1	-138/+2183
	Django 1.3’s focus has mostly been on resolving smaller, long-standing feature requests, but that hasn’t prevented a few fairly significant new features from landing, including: * A framework for writing class-based views. * Built-in support for using Python’s logging facilities. * Contrib support for easy handling of static files. * Django’s testing framework now supports (and ships with a copy of) the unittest2 library.
2010-12-28	Update to Django 1.2.4:	joerg	1	-15/+8
	- Fix a bug in the admin interface that could leak informations to users with staff privileges bypassing lookup arguments in the query string. - Fix a bug for running the test suite in a multi-db setup - Deprecated django.contrib.gis.tests.run_gis_tests()
2010-09-13	Update to django 1.2.3 to fix problems of the 1.2.2 security fix:	joerg	1	-1/+5
	- Properly deal with non-ASCII responses in the CSRF code - Restore compatibility with certain forms like the user-editing form in admin Reduce maintainance overhead in pkgsrc by providing PLIST print magic.
2010-09-09	Changes 1.2.2:	adam	1	-1/+38
	As of the 1.2 release, the core Django framework includes a system, enabled by default, for detecting and preventing cross-site request forgery (CSRF) attacks against Django-powered applications. Previous Django releases provided a different, optionally-enabled system for the same purpose. The Django 1.2 CSRF protection system involves the generation of a random token, inserted as a hidden field in outgoing forms. The same value is also set in a cookie, and the cookie value and form value are compared on submission. The provided template tag for inserting the CSRF token into forms -- {% csrf_token %} -- explicitly trusts the cookie value, and displays it as-is. Thus, an attacker who is able to tamper with the value of the CSRF cookie can cause arbitrary content to be inserted, unescaped, into the outgoing HTML of the form, enabling cross-site scripting (XSS) attacks. This issue was first reported via a public ticket in Django's Trac instance; while being triaged it was then independently reported, with broader description, by Jeff Balogh of Mozilla.
2010-06-16	Django 1.2.1:	joerg	1	-128/+778
	- Support multiple database in one Django instance - Model validation inspired by the Form validation - Vastly improved protection against Cross-Site Request Forgery - New user "message" framework, incl. support for anonymous users - Hooks for object-level permissions and permissions for anonymous users - Customization of e-mail sending via the new e-mail backend - Smarter if template tag
2010-02-11	Add an option for the oracle backend.	joerg	1	-1/+19

2010-02-10	Use pgsql as option name for consistency with other packages.	joerg	1	-31/+31

2010-02-10	Retire psycopg1 option and rename psycopg2 to postgresql, making it	joerg	1	-31/+31
	the default. Bump revision.
2009-10-19	Update to Django 1.1:	joerg	1	-44/+177
	- Support for aggregates and query expression in the ORM - Suport for unamanged models and proxy models - Support for deffered fields - Mark individual fields as editable in the admin; support for custom actions - Better support for Last-Modified/ETag - Improved GIS support - {% for %} now has an {% empty %} to simplify handling empty lists - Various smaller improvements
2009-07-29	Update to Django 1.0.3:	joerg	1	-1/+10
	- various bugfix - correctly validate file names for the admin media when using the development server
2009-06-14	Convert @exec/@unexec to @pkgdir or drop it.	joerg	1	-274/+1

2009-01-30	Also remove some more directories on deinstall.	joerg	1	-1/+5

2009-01-29	Fix PLIST. No idea how that slipped through testing.	joerg	1	-3/+12

2008-09-04	Update Django to newly released version 1.0, fixing a cross-site request	tonnerre	1	-163/+1334
	forgery vulnerability described in http://www.djangoproject.com/weblog/2008/sep/02/security/ .
2008-04-12	Convert to use PLIST_VARS instead of manually passing "@comment "	jlam	1	-65/+65
	through PLIST_SUBST to the plist module.
2007-08-11	Add the variations of the plist for the various options back.	joerg	1	-33/+65
	Bump revision.
2007-08-09	Update to Django 0.96:	joerg	1	-1109/+1208
	The main goal of the 0.96 release is to cleanup and stabilise the features from 0.95. Incompatible changes: - constraint names changed in some cases, this can effect manage.py reset on old databases - some names in manage.py changed - backslash escaping is done more consistently - ENABLE_PSYCO is gone Important changes: - merge of newforms - URLconf takes normal callables - new test framework - passwords for users can be entered as normal text in the admin interface, no need to hash manually In addition: dropped py-setuptools dependency.
2007-02-19	Fix installation when only psycopg2 support is requested, the postgres	joerg	1	-1109/+1109
	code is shared with psycopg1. Include a small patch to make keyword mistakes in query args much more obvious (from django svn). Other users might be as stupid as the maintainer. Bump revision.
2007-01-25	Update Django to 0.95.1. Changes:	joerg	1	-1109/+1109
	* A patch for a small security vulnerability in the script Django's internationalization system uses to compile translation files. * A fix for a bug in Django's authentication middleware which could cause apparent "caching" of a logged-in user. * A patch which disables debugging mode in the flup FastCGI package Django uses to launch its FastCGI server, which prevents tracebacks from bubbling up during production use.
2006-09-11	Import Django 0.95 from pkgsrc-wip:	joerg	1	-0/+1110
	Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. Django was designed to make common Web-development tasks fast and easy.