python-mongoengine
No description set
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:seife:Factory/python-mongoengine && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
python-mongoengine.changes | 0000006246 6.1 KB | |
python-mongoengine.spec | 0000001960 1.91 KB | |
v0.24.0.tar.gz | 0000327979 320 KB |
Revision 4 (latest revision is 8)
Dominique Leuenberger (dimstar_suse)
accepted
request 959858
from
Dirk Mueller (dirkmueller)
(revision 4)
- update to 0.24.0: * EnumField improvements: now ``choices`` limits the values of an enum to allow * Fix bug that prevented instance queryset from using custom queryset_class #2589 * Fix deepcopy of EmbeddedDocument #2202 * Introduce a base exception class for MongoEngine exceptions (MongoEngineException). Note that this doesn't concern the pymongo errors #2515 * Fix error when using precision=0 with DecimalField #2535 * Add support for regex and whole word text search query #2568 * Add support for update aggregation pipeline #2578 * BREAKING CHANGE: Updates to support pymongo 4.0. Where possible deprecated functionality has been migrated, but additional care should be taken when migrating to pymongo 4.0 as existing code may have been using deprecated features which have now been removed #2614. For the pymongo migration guide see: https://pymongo.readthedocs.io/en/stable/migrate-to-pymongo4.html. In addition to the changes in the migration guide, the following is a high level overview of the changes made to MongoEngine when using pymongo 4.0: - limited support of geohaystack indexes has been removed - ``QuerySet.map_reduce`` has been migrated from ``Collection.map_reduce`` and ``Collection.inline_map_reduce`` to use ``db.command({mapReduce: ..., ...})`` and support between the two may need additional verification. - UUIDs are encoded with the ``pythonLegacy`` encoding by default instead of the newer and cross platform ``standard`` encoding. Existing UUIDs will need to be migrated before changing the encoding, and this should be done explicitly by the user rather than switching to a new default by MongoEngine. This default will change at a later date, but to allow specifying and then migrating to the new format a default ``json_options`` has been provided. - ``Queryset.count`` has been using ``Collection.count_documents`` and
Comments 0