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

Future of PyQRCode NG? #16

Open
heuer opened this issue Jan 6, 2020 · 9 comments
Open

Future of PyQRCode NG? #16

heuer opened this issue Jan 6, 2020 · 9 comments
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@heuer
Copy link

heuer commented Jan 6, 2020

While I think that PyQRCodeNG is the better PyQRCode it has not yet achieved great popularity.

Why is it not accepted? Is it worth investing more energy in the project?

Not having received the project name "pyqrcode" is IMO the biggest problem.
Should that be tried again, c.f. pypi/warehouse#4121? As soon as Michael replies that he intends to maintain PyQRCode, the request is rejected again, though.

Ideas? Thoughts?

@heuer heuer added help wanted Extra attention is needed question Further information is requested labels Jan 6, 2020
@om26er
Copy link

om26er commented Jan 16, 2020

I think it absolutely makes sense to maintain this fork and the effort needs to be made to reclaim the original name. Seems like the original developer hasn't made much activity on GitHub for a while.

@heuer
Copy link
Author

heuer commented Jan 16, 2020

Thanks for your feedback.
Currently I am not in the mood to maintain a lib which nobody uses.
The current version of PyQRCode NG is IMO better than PyQRCode but if users continue to rely on the predecessor, I see no reason to maintain this library.
I see many advantages over the predecessor, in particular, all pull requests have been incorporated and the processing speed has been improved. Especially for PNG (twice as fast)

chart

Anyway, I have also another QR Code generator, Segno, which is maintained and every minute I spend on this project, I lose for my project.

Maybe Michael comes back and merges the improvements (pull requests and my work) into the PyQRCode project... . Otherwise I see no basis to continue this project, unless it has more users or it is continued under the name pyqrcode.

@heuer
Copy link
Author

heuer commented Jan 17, 2020

My (biased) opinion: I understand the attraction of PyQRCode, it has a nice name and the API is much better than the popular qrcode lib which requires too much boilerplate code and injects a lot of dependencies (especially PIL/Pillow). But PyQRCode is unmaintained and dead slow.
Segno provides also a simple API (IMO) and is faster, standard-compliant, introduces no dependencies and provides more features.

@heuer
Copy link
Author

heuer commented Jan 17, 2020

See also mnooner256#52 and mnooner256#55

@heuer
Copy link
Author

heuer commented Jan 21, 2020

On a sentimental mood, I agreed to continue this project, but after the fork, it found no significant number of users.
I am now giving up this project unless more users find it attractive. It steals too much of my time and I'm too attached to my own project.

If someone is interested in maintaining the project, I offer my help, though.

@clach04
Copy link

clach04 commented Apr 27, 2020

@heuer many thanks for your work on this, I understand you wanting to focus you efforts. I've posted #17 - any objections to approving it? It would make discovery of your (maintained) project easier for people who stumble across this.

It took me a while to discover this when I was looking for a text based qrcode generator (I ended up creating mnooner256#73 in an attempt to help reduce time for others).

@heuer
Copy link
Author

heuer commented Apr 27, 2020

Thanks, @clach04, your patch is already merged

@ghost
Copy link

ghost commented Aug 8, 2021

I just found out about this library. pyqrcode is definitely unmaintained.

I see you have segno as well, which has type hints. I'm just looking for QR codes for the terminal at this time. Which of the two do you think I should use?

@clach04
Copy link

clach04 commented Aug 12, 2021

@sometato really your call. Both are excellent and have stable APIs that work really well.

I have written using both but segno is my preferred one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants