-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Towards 1.0
Matthieu Rigal edited this page May 7, 2015
·
6 revisions
We all wish to arrive to a feature-full and stable version as soon as possible, but the Road is still quite long. Here are a couple things we should address before thinking to bring out a 1.0 version:
- ListField, especially default and nullify behaviour, check the [Issue label] (https://github.com/MongoEngine/mongoengine/issues?q=is%3Aopen+is%3Aissue+label%3AListField)
- DecimalField, maybe simply better documentation, check the [Issue label] (https://github.com/MongoEngine/mongoengine/issues?q=is%3Aopen+is%3Aissue+label%3ADecimalField)
- GridFS, imperfect support, check the [Issue label] (https://github.com/MongoEngine/mongoengine/issues?q=is%3Aopen+is%3Aissue+label%3AGridFS)
- De-/Referencing, inconsistent behaviour, performance concerns, check the [Issue label] (https://github.com/MongoEngine/mongoengine/issues?q=is%3Aopen+is%3Aissue+label%3A%28De%29Reference)
- Aggregation Framework, use it, recommend over Map-Reduce and implement new functionalities, check the [Issue label] (https://github.com/MongoEngine/mongoengine/issues?q=is%3Aopen+is%3Aissue+label%3A%22Aggregation+Framework%22)
- Connection(Client), how we use it, how we test it, check the [Issue label] (https://github.com/MongoEngine/mongoengine/issues?q=is%3Aopen+is%3Aissue+label%3AClient%2FConnect)
- Index creation: we support almost all possible way to create index, the corresponding code is dirty and poorly comprehensible. Time for a cleanup and clearness on how to use it.
- Implement PyMongo 3.X optimizations, mainly bulk possibilities
- Automatic testing of various MongoDB versions
- Work on performance, some open issues are about this point, also checking MongoMallard: the elasticsales fork loses some features but is very performant because it doesnt cast everything into Document objects all the time.
- Search support - native support of search
- Unique Python code-base, get rid of 2to3, using six?
- Drop Python 2.6 support, update the test to use cleaner assertIn, assertIsNone, use with() context managers where it is possible
- Drop PyMongo 2.X support? Why not, it will probably be more than one year old and support connections to MongoDB 2.X
- Drop MongoDB 2.4 support? 3.2 (or more) may be out by that time