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

Merge with fakeredis package #177

Open
cunla opened this issue Apr 25, 2023 · 1 comment
Open

Merge with fakeredis package #177

cunla opened this issue Apr 25, 2023 · 1 comment

Comments

@cunla
Copy link

cunla commented Apr 25, 2023

Hi,

I am the maintainer of fakeredis.
I noticed that redislite is not maintained, and I was wondering who can I talk with regarding merging the two packages.
A lot of the issues here are addressed by fakeredis.

Thanks,
Daniel

@steve-mavens
Copy link

I would be excited if "merging" with fakeredis meant that fakeredis gained a mode in which it behaves like redislite, in the sense of using the actual redis-py code, connected to a version of the actual Redis code. People can (and do) argue all day about unit tests vs partial integration tests, and which combinations of units should be tested together. The ability to automatically generate integration tests from unit tests by changing what you patch, is really useful. Doing it all through a single Python test package would be very convenient.

Of course the redislite-like mode would not be pure-python, and presumably it wouldn't run directly on Windows. So I understand if it's not what you have in mind! The same thing can be achieved by writing different test fixtures for the different configurations: it's "just" a bunch of dependencies for each project to manage.

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

No branches or pull requests

2 participants