washeck

@SmileyChris can this please be merged and released? It is blocking upgrade to Django 5.0 (I am testing RC1 now). Thank you.

Yes, that's what I'm doing (`django_5.0` branch from your fork) and it's working so I think it would be good to issue the release before Django 5.0 is released and...

Fix is available but not merged: https://github.com/SmileyChris/django-countries/pull/438

@JulianTenschert @eatsleepdeploy @josepduarte and others: please stop spaming the issue with "Me too" comments. It's just filling everyone's inboxes and adding zero value. In the very first comment there is...

Hi, I don't agree with grimwm's wording. I'd like to thank the authors for the work they put into maintenance of this library. On the other hand, we also had...

The thing is that, as a random contributor, it is difficult to guess it the maintainers prefer to revert the PR or fix it. So is sending a PR with...

Well, until this is fixed, we cannot use `safety` because there is no way for the new and old pydantic to cooexist in one project and we cannot drop library...

@yeisonvargasf What is the recommended solution at the moment? We are a paying custumer of PyUp.io and we want to switch from `pipenv check` to a tool working in `poetry`....

@jrief Thanks for merging https://github.com/jrief/django-sass-processor/pull/180 May I ask you to issue a new release with the fix? It would make my life a bit easier with testing our project for...

I think "Fix compatibility with Django 5.1dev" would be enough