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

[dezanche]

@blink1073:
I ran into the problem of different bson modules installed under the same name (last one overwrites the previous one).
E.g., pip install bson followed by pip install pymongo will leave you with the version that comes with PyMongo.
There are workarounds (painful hacks IMO) but this needs to be cleared up.
I personally need to use the PyMongo one because it implements dates as described in the standard. But I don't need all of PyMongo, so BSON should be a separate package.
It also doesn't seem proper form for pip to install 2 different modules in separate directories from a single install command.

[benoit74]

@blink1073 thank you for proposing help on this repo.

From my perspective, it now looks clear that @Parkayun has currently abandoned this repo / Python package.

I would love if PyMongo team accepts to publish a separate standalone bson package (with another name obviously ...) and depend on that from pymongo.

On my end I've resorted to use the full pymongo on my projects for the time being, this package seems to abandoned to not feel at risk, which is kinda sad but looks like the hard truth.

[dezanche]

There is a process through PyPI Support
IMO the ideal would be that this project becomes the py-bson package, and PyMongo takes over the bson name and publishes it as a separate package.

[blink1073]

Thank you both for the suggestions, I've opened https://jira.mongodb.org/browse/PYTHON-5636 for our team to discuss.

[blink1073]

After discussion, we do not wish to attempt a PEP-541 request for bson or pybson. We think the best outcome to reduce confusion would be for @Parkayun to archive the bson package on pypi and continue to publish pybson.