Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider renaming? #41

Open
canni opened this issue Jun 23, 2016 · 5 comments
Open

Consider renaming? #41

canni opened this issue Jun 23, 2016 · 5 comments
Milestone

Comments

@canni
Copy link

canni commented Jun 23, 2016

I have a project witch among others depends on 2 libraries, one of them depends on standalone bson package, and other depends on pymongo.

Now because pymongo from unknown to me reasons also exposes top-level bson module, with different API; this creates a shadowing problem, that is dependent on order of dependencies installation :/

Currently to get around it I have to do on my top-level package monkey-patching like that:

import bson
bson.loads = bson.BSON.decode
bson.dumps = bson.BSON.encode

Could we consider renaming the top-level package, with an alias for BC?

@Parkayun
Copy link
Member

Nice idea. We can consider to add alias, not renaming.

@canni
Copy link
Author

canni commented Jun 24, 2016

That won't solve my case, but it's good enough, it might be good to also mention this inconsistency on pypi page (mongo docs already warn about name collision with this package)

@Parkayun Parkayun added this to the 0.5 milestone Jun 24, 2016
@Parkayun
Copy link
Member

#29

@Parkayun
Copy link
Member

I will change name to pybson.

import pybson

@Parkayun
Copy link
Member

Parkayun commented May 19, 2020

I uploaded pypi which names pybson
It just for looking demands.
if it has not enough demand, I can't maintain pybson name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants