Branch: refs/heads/master
Home: https://github.com/django/django
Commit: d8d61d8260badd87b85accaf5776587f2d355c10
https://github.com/django/django/commit/d8d61d8260badd87b85accaf5776587f2d355c10
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M tests/fixtures/tests.py
M tests/serializers/tests.py
Log Message:
-----------
Added tests for missing pyyaml.
This test makes sure an YAML import errors are communicated to the
caller rather than stating the serializer does not exist.
Commit: c72392dab4b4cf6f5d9b35a3dcb582fbfe38ebb8
https://github.com/django/django/commit/c72392dab4b4cf6f5d9b35a3dcb582fbfe38ebb8
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M django/core/serializers/__init__.py
Log Message:
-----------
Added yaml directly into BUILTIN_SERIALIZERS.
The serializer definitely exists, but the dependent yaml module may not
be installed. The register_serializer() function will catch exceptions
and will stub in a fake serializer object that will raise the exception
when the serializer is used.
Commit: 076cf131ec8084ce6d9cc3a05b0f4bcc167d6cbc
https://github.com/django/django/commit/076cf131ec8084ce6d9cc3a05b0f4bcc167d6cbc
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M django/core/management/commands/dumpdata.py
Log Message:
-----------
Moved get_serializer() call in dumpdata command.
Moved the get_serializer() call within the condition that checks public
serializers. This will allow exceptions other than
SerializerDoesNotExist to be raised in order to provide the caller with
useful information, e.g when pyyaml is not installed.
Commit: ca3ac4a3e37cc844bef7f7553c6b1a6cc642e6e6
https://github.com/django/django/commit/ca3ac4a3e37cc844bef7f7553c6b1a6cc642e6e6
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M tests/serializers/tests.py
Log Message:
-----------
Updated NoYamlSerializerTestCase to run with yaml.
In order to verify the behavior of using the yaml serializer when yaml
is on the system, fake the ImportError when the serializer is being
registered.
Commit: 0ac5e8d8e945b2232333fd777e7684c4c2c68316
https://github.com/django/django/commit/0ac5e8d8e945b2232333fd777e7684c4c2c68316
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M AUTHORS
Log Message:
-----------
Added name to AUTHORS (per Russell Keith-Magee)
Commit: 9587d4eea09bc8d8a852dfb24c2a9227c74fd8ad
https://github.com/django/django/commit/9587d4eea09bc8d8a852dfb24c2a9227c74fd8ad
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M tests/serializers_regress/tests.py
M tests/timezones/tests.py
Log Message:
-----------
Fixed existing tests to handle BadSerializer.
When a BadSerializer instance is stubbed in for the yaml serializer,
make sure tests do not fail.
Commit: 01a5359477fbc82488dddf9476581fe72c049b51
https://github.com/django/django/commit/01a5359477fbc82488dddf9476581fe72c049b51
Author: Roberto Aguilar <robe...@baremetal.io>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M AUTHORS
M django/core/serializers/__init__.py
M tests/fixtures/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
Log Message:
-----------
Cleanup commit after peer review.
Commit: 4f5faa1916e7c8cb72cc9ebf1a1fd964ba6e707b
https://github.com/django/django/commit/4f5faa1916e7c8cb72cc9ebf1a1fd964ba6e707b
Author: Russell Keith-Magee <russ...@keith-magee.com>
Date: 2013-09-06 (Fri, 06 Sep 2013)
Changed paths:
M AUTHORS
M django/core/management/commands/dumpdata.py
M django/core/serializers/__init__.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py
M tests/timezones/tests.py
Log Message:
-----------
Merge pull request #1582 from
rca/12756-missing-yaml-module-serializer-error-message
Fixed #12756: Improved error message when yaml module is missing.
Compare: https://github.com/django/django/compare/9b2dc12b8332...4f5faa1916e7
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/522a5fa22bf3e_3f8af39d50773a2%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.
