Skip to content

Conversation

@szuliq
Copy link

@szuliq szuliq commented Jun 24, 2016

Right now the port is dropped from connection settings even if MongoReplicaSetClient is not being used.


This change is Reviewable

Right now the port is dropped from connection settings even if `MongoReplicaSetClient` is not being used.
@wojcikstefan
Copy link
Member

Thanks for this @szuliq! Could you elaborate on the issues this is causing if port is dropped for PyMongo 3+'s MongoClient? Is there a unit test we can run to show the problem?

@wojcikstefan
Copy link
Member

This is superseded by #1436

@szuliq
Copy link
Author

szuliq commented Dec 13, 2016

Sorry I didn't comment on this. Somehow I didn't notice it in my mailbox.

TBH I don't remember right now. We've had some strange issue one time and I investigated it, found this bug and opened this PR.

Good thing you've fixed it. Thanks!

@szuliq szuliq deleted the patch-1 branch December 13, 2016 09:14
@Davidrjx
Copy link
Contributor

@szuliq hi, i do not know why port in MongoReplicaSetClient for pymongo 2.x was droped.
as pymongo source code shows, port as kwargs is passed and can be used to update connection setting.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants