This package provides a FAKE mongoDB implementation and is quite handy for testing.
CHANGES
1.0.1 (2015-03-17)
bugfix: reflect changes in pymongo > 2.8.0. The dta basename checker method _check_name method was moved from pymongo.database to pymongo.helpers. Make import work for all pymongo versions.
1.0.0 (2013-03-06)
Added support for Python 3.3.
Dropped support for Python 2.4 and 2.5.
0.2.1 (2013-02-02)
added realistic FakeCollection.remove return values
bugfix around FakeCollection.save
0.2.0 (2012-12-16)
feature: support pymongo 2.4 API and support new safe write concern
include m01.stub for testing mongofake components and compare with real pymongo output. Use –all option for real pymongo and mongodb tests.
implemented some basic tests and run them with m01.stub and m01.mongofake libraries
implemented correct response for collection update method based on new pymongo 2.4. More will follow if more tests get implemented
switch from lovely.importchecker to p01.recipe.setup importchecker which doesn’t warn about bad svn url during buildout process
0.1.1 (2012-12-10)
inproved dictify method, also convert single SON object to dict
add some initial tests
0.1.0 (2012-05-22)
First independent release from m01.mongo.testing
Release files for m01.mongofake 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| m01.mongofake-1.0.1.zip | 22.8 kB | Without provenance | Details |
Release files / m01.mongofake-1.0.1.zip
| Download URL | m01.mongofake-1.0.1.zip |
|---|---|
| Size | 22.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e63a34b7aea60996354791016aab62e489679dca885682f5587ec63b4304362
|
|
BLAKE2b-256 checksum How to use checksums |
0f42704712218c2d7204fd7133644ba618a85d9041fd063a643ec779e74f818e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for m01.mongofake 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
