-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
ugettext_lazy breaks with Django 4.0 alpha 1 release #399
Comments
Related to #381 |
Should also include wheels in the next release: #382 |
If @jonathan-s is no longer maintaining this project, there may need to be a new community fork. There have been no commits for a year. |
May be @jonathan-s can give us is idea about that ? I'm interesting by going forward on this subject |
@pulse-mind Probably what needs to happen is someone volunteers to fork, merges in the necessary 4.0 compatibility patches, and publishes under an available name on PyPI such as |
@johnthagen why using a fork, it would be better to have the rights on the repo to do the job?!? |
Ideally yes, but if the maintainers are not responsive, there is no one to grant anyone new permissions to this repo. |
Agree with you. May be some others users like @ZuluPro may know something ? Is it possible to know the list of the members who have this kind of permissions ? |
Hi everyone, I absolutely don't have the time to maintain DBBackup but it would be a pleasure to pass the ownership to someone with more time and knowledge. Who's volunteer to maintain DBBackup ? |
I have enough time to do very basic maintenance (keep dbbackup working on latest Django / remove deprecation warnings / etc.) I'm currently doing the same for If you also want to grant ability to upload to PyPI my username there is: https://pypi.org/user/johnthagen/ |
Thank you @johnthagen and @ZuluPro !! If you need help, let me know! |
Hey @ZuluPro I'm coming over from the Jazzband GitHub organization. We're currently the biggest organization for OSS Django packages. I would be interested in taking temporary ownership for this repo and doing the necessary changes to get it transferred to Jazzband. Including myself, there are various members that I'm sure would support maintenance for this repo. |
Hi @Archmonger Hi @johnthagen But like @Archmonger suggested, it could be a good thing to transfer it to Jazzband |
I also agree Jazzband would be a very good long term plan. Thanks @ZuluPro! |
Let me know if you need any support on this! |
Hi @Archmonger |
I'm currently working on cleaning things up for a release.
I think another issue with a checklist of what needs to be done to get this repo ready for submission to JazzBand, would be very helpful. |
@ZuluPro I'm pulling together a Would you mind double checking if I was invited to the PyPI project? I'm also not sure where I would "see" invites. I've looked through all of the pages on my PyPI account and don't see anything about My profile: https://pypi.org/user/johnthagen/ |
Bump. @ZuluPro Would you please look in on this? Django 4.0 is released. |
I have the ability to create releases and will do so once @johnthagen tags a solid build |
I see, @johnthagen Do you see that @Archmonger is prepared to publish a release? @Archmonger Can you clarify whether you consider a beta release, like the one @johnthagen mentioned above ( |
I just confirmed that john had not been invited to PyPI, so I've sent him an invite. I am currently not a maintainer on the GitHub repo though so I'll need @johnthagen to add me as one if I am to tag releases in the future. |
@Archmonger Thank you for looking at that. I appreciate any further cooperation needed to get a Django 4.0-compatible release out the door. |
As a temporary workaround, you can install pip install via git ex |
Thanks!
@Archmonger You have been invited as an owner to the
|
I know this issue is closed, but any word on getting an official release? Appreciate the beta version. |
Please follow #415. Unfortunately we are still waiting for the original maintainers to give access to the ReadTheDocs site. |
Can a release be made including #342 (replace
ugettext_lazy
withgettext_lazy
)?The newly released Django 4.0 alpha 1 has dropped
ugettext_lazy
.The latest release of django-dbbackup still uses
ugettext_lazy
. This was addressed in #342 however not yet released, meaning of dbbackup run into errors and can not try their applications on Django 4.0 alpha 1 until this is done.The text was updated successfully, but these errors were encountered: