Noah Stapp
Noah Stapp
@weiqingy My team is very interested in this change, as we are looking to move our Samza application to Kubernetes. Is this still being actively worked on? We're interested in...
> I think there's still a test failure: [spruce.mongodb.com/task/mongo_python_driver_test_macos_python3.9_test_rapid_sharded_cluster_auth_ssl_async_patch_3e2967147e0fb857160205341e207b03c2eac87b_67b4ceab59e13500077b1df3_25_02_18_18_17_17/tests?execution=0&sortBy=STATUS&sortDir=ASC](https://spruce.mongodb.com/task/mongo_python_driver_test_macos_python3.9_test_rapid_sharded_cluster_auth_ssl_async_patch_3e2967147e0fb857160205341e207b03c2eac87b_67b4ceab59e13500077b1df3_25_02_18_18_17_17/tests?execution=0&sortBy=STATUS&sortDir=ASC) Looks like a transient failure, it went away on a retry.
The test failure is also present in master, tracked in https://jira.mongodb.org/browse/PYTHON-5198.
Still seeing some failures on Windows.
> Can we remove the top level `test_logger.py` as part of this? Good point, I've added automated running of the `test/synchronous` directory to https://github.com/mongodb/mongo-python-driver/pull/1699 so we can start removing the...
> @NoahStapp this should be ready for an update now. Updated, still need https://github.com/mongodb/mongo-python-driver/pull/1718 to be merged for the final version.
Hi @Mte90, What use-case are you trying to solve with this request? The purpose of this project is to provide the skeleton of a full-stack application. Removing the frontend doesn't...
Is this still an issue? [LazyReferenceField](https://docs.mongoengine.org/apireference.html#mongoengine.fields.LazyReferenceField) and the [no_dereference](https://docs.mongoengine.org/apireference.html#mongoengine.context_managers.no_dereference) context manager have both been added since this was reported. LazyReferenceField in particular appears to specifically call out this use case...
> Does your benchmark still apply? You seem to have changed the code substantially, and I would assume that the `to_python` caching you do at the top level not to...
> > > Does your benchmark still apply? You seem to have changed the code substantially, and I would assume that the `to_python` caching you do at the top level...