-
Notifications
You must be signed in to change notification settings - Fork 83
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
Is this project still active? #122
Comments
+1 |
1 similar comment
+1 |
I think the lack of response on this thread gives you the answer It's a shame, because this and exif are the only two decent python EXIF modules, and I've hit blockers with both modules, and both seem to be abandoned. |
There's a ton of tags missing in this project. I tried to use it to read some tags and it didn't know about them. For the most complete I'd recommend checking https://github.com/exiftool/exiftool/ |
@darkvertex exiftool is the gold standard of EXIF modules. I've used it in the past as part of a Perl project, but Perl doesn't get a lot of love these days. @hMatoba this module is too important to abandon. I totally understand if you're too busy to maintain this, or if you no longer use it yourself, but could you add some other maintainers to this repo so they can do some maintenance, merge some PRs, etc. I'd be happy to volunteer. It seems neater to add collaborators here than to create yet another fork. Thanks |
Judging by @hMatoba's Github profile, there are zero contributions to any project since 2019 and their blog is no longer online. Safe to assume this module is dead. I'm reluctantly going to fork it and publish under a different name on PyPI... I'm no developer but I can at least read and respond to issues/PRs and keep the module going. I just can't hold up my project any more. |
@djjudas21 good timing as I just found this project too. If you want I'm happy to fork it to my company's GitHub organization (and add you as a maintainer) in case you don't want it attached to your personal GitHub account. Either way instead of re-publishing to PyPi under a different name we should request a name transfer. |
I would be happy to be a co-maintainer on this project |
@davetapley ah great, I didn't know you could do a name transfer. Please go ahead and do that - I'm happy to be a maintainer although I'm not developer. Seems like it will be a better home to have it in a company namespace than a personal one. |
Okay forked to https://github.com/JEFuller/Piexif
|
Thanks @davetapley. I've 👍 your issue with PyPI |
Update:
|
Update: The PyPi project has been transferred to me: pypi/support#2065 (comment). In the coming days I will issue a new release to update ⬇️ and thereafter please use https://github.com/JEFuller/Piexif/issues Line 23 in 3422fbe
|
Thanks for your perseverance @davetapley. Look forward to a release in its new home 👍 |
Making progress, follow along here: https://github.com/JEFuller/Piexif/projects/1 I won't post here again until new release is pushed. |
@davetapley are you still maintaining the library? I get a 404 on the last link you posted. I've noticed a mistake in the docs, and I was going to fix it, but I'm not sure how active this lib is. |
@Erotemic yes, but not actively, I'm not at a computer right now, but I think there was another package which I started using, but I can't remember the name. |
I see there hasn't been an update to the code for a couple of years, there are a bunch of issues with no response, and several outstanding pull requests. Not to blame anyone, because I know everyone has too many things to keep up with :)
I like how Piexif works, and would like to see it continue to be supported, so wanted to check about its likely future...
The text was updated successfully, but these errors were encountered: