Maintain one to one match with original Mongo code

[benoit74]

Current implementation seems to be fairly different than the one from Mongo at https://github.com/mongodb/mongo-python-driver

Is there any reason for this difference ? I checked their code and found no dependencies between the bson package and other packages in their repo.

Would it make sense that we automate something like this:

• for every release of https://github.com/mongodb/mongo-python-driver, we "clone" (more or less a cp, there is not automated tool for this as far as I know) the bson package in this repo
• this clone is then used to perform releases of pymongo, with version number in line with the one of mongo

This would have many benefits:

• very limited maintenance effort on this repo (all issues can be directly adressed to mongo)
• no extra documentation need, we can use the original Mongo doc
• lot's of know how around original bson package already disseminated on the net
• more visibility / confidence in using this project (for now in my organization we are still using pymongo in multiple projects just because we need bson to properly handle datetime serialization for instance)

WDYT?

[benoit74]

And I can definitely help on this change. We will probably do it anyway, it just makes a little more sense to me to help enhance existing stuff if there is any interest rather than create "yet another thing".

[blink1073]

Hi @Parkayun, I'm the current lead of the PyMongo team. We have seen several cases where users are trying to install both PyMongo and bson, sometimes unintentionally, and getting import errors since the submodules differ. Would you consider one of the following paths forward?

• Accept PRs from our team to keep the two libraries in sync
• Move ownership of bson to our team and we can publish a separate bson package and depend on that from pymongo