destream-py / destream Goto Github PK

During the attempt to convert the test suite to PyTest, I have discovered, that the two tests:

• test_10_passing_file_object
• test_20_passing_filename

from

were identical. What should be the difference between them, @cecton ?

https://github.com/destream-py/restoredb.py

This one is particularly old. StreamDecompressor was the old name of destream.

If you dont want to maintain it it's okay you can archive the repo. I'm not sure if it is used by anyone at all tbh.

I will move the ownership on pypi to you @jruere and @eumiro . Thanks a lot again for adopting destream ❤️

It would be nice.

I suggest you add a CoC so the project stay welcoming and protected from abuse.

Click here to add one: https://github.com/destream-py/destream/community/code-of-conduct/new?template=contributor-covenant

You will need to provide the email address of someone who can take action in case of problem.

Hello everyone,

destream is a creation of mine and I started it when I didn't have much experience in open source projects. I have recently improved the quality of this repo by using semantic versioning and fixing the thread related issue.

If you have any idea on how to improve the quality of this product (automatic delivery, coverage, testing, better classes, naming convention... anything) feel free to propose changes.

I need you more than you need me, especially since I don't even use this library anymore for now.

Best

Are there plans to support Python 3?

I checked that the current code does not have this print.

Please, release a new version without the print.

Hi everyone 👋

I am glad that this project helped some people managing archives. Unfortunately it is now time for me to move on. One of the main reason is that I didn't have a use for this library for a very long time now. Another reason is that I don't use much Python anymore either.

I believe a team of interested people can bring this project to the next level with more features, better code quality and better stability and tests.

That's why I think this project should go back to the community. I would like to create an organization with a few maintainers and owners for it. The more the merrier. If you are interested in adopting destream, please let me know.

Kind regards and thank you for your interest

cc @jruere @ziord @gauravssnl @luenix @ayoshi @Phyllostachys @shekkbuilder @Meroje

I propose, as @eumiro recommended, that we drop the support of the Python versions that are in end of life. There is nothing we can do against that anyway. (Then I promise I won't give you more work 😁 )

cc @jruere

Using:

• Python 3.6
• destream==5.0.0
• python-magic==0.4.18

I think it probably broke when I moved the repository.

I tried to re-enable it but it has difficulties to find the organization for some reason.

Maybe someone else can give it a try?

I don't know if it is possible but it would be nice to have a GitHub Actions enforcing it on the PR so it will give less work to the maintainers.