django: Rename django_1_3_2 to django_1_3.
The django team tries very hard to not introduce backwards-incompatible changes into patch versions, so I guess it is safe to only use the major and minor version number for specific Django versions. This way, it doesn't require manual action by users who have added django_1_3_* into system packages or local overrides/custom derivations. Thanks to @7c6f434c for the suggestion.
This commit is contained in:
parent
36fc363a47
commit
10d92ca988
@ -523,7 +523,7 @@ let pythonPackages = python.modules // rec {
|
||||
};
|
||||
|
||||
|
||||
django_1_3_2 = buildPythonPackage rec {
|
||||
django_1_3 = buildPythonPackage rec {
|
||||
name = "Django-1.3.2";
|
||||
|
||||
src = fetchurl {
|
||||
@ -548,7 +548,7 @@ let pythonPackages = python.modules // rec {
|
||||
md5 = "24b8373916f53f74d701b99a6cf41409";
|
||||
};
|
||||
|
||||
propagatedBuildInputs = [ django_1_3_2 ];
|
||||
propagatedBuildInputs = [ django_1_3 ];
|
||||
|
||||
meta = {
|
||||
description = "A database schema evolution tool for the Django web framework";
|
||||
@ -565,7 +565,7 @@ let pythonPackages = python.modules // rec {
|
||||
sha256 = "1hhvpi81yknvlaazq1cpgamp9vf3x1fcr0ba64q3j2yz1kgin1i8";
|
||||
};
|
||||
|
||||
propagatedBuildInputs = [ pkgs.pil django_1_3_2 ];
|
||||
propagatedBuildInputs = [ pkgs.pil django_1_3 ];
|
||||
|
||||
meta = {
|
||||
description = "A collection of useful extensions for Django";
|
||||
@ -2072,7 +2072,7 @@ let pythonPackages = python.modules // rec {
|
||||
|
||||
propagatedBuildInputs =
|
||||
[ recaptcha_client pytz memcached dateutil paramiko flup pygments
|
||||
djblets django_1_3_2 django_evolution pkgs.pycrypto python.modules.sqlite3
|
||||
djblets django_1_3 django_evolution pkgs.pycrypto python.modules.sqlite3
|
||||
pysvn pkgs.pil psycopg2
|
||||
];
|
||||
};
|
||||
|
Loading…
x
Reference in New Issue
Block a user