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

Recent Django / Python improvements #51

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Recent Django / Python improvements #51

wants to merge 5 commits into from

Conversation

WhyNotHugo
Copy link
Contributor

@WhyNotHugo WhyNotHugo commented Jun 2, 2020

  • Stop using deprecated smart_text, which is a warning on Django 3.0, and will fail with the next major release (note: smart_str is already present in Django 1.11, so this doesn't drop support for that). Django 1.11 won't work on recent (and not-so-recent) versions of Python, so drop that too. It's already past its EOL too.
  • Drop Pythons that have reached EOL.
  • Add newer Pythons to CI, and the README (side note; I've been using this with Django 3.0 on Python 3.8 for months with no issues, so just making support official).

Note: Projects that can't update for some reason can still use older versions of this library anyway, anyone using such old Pythons/Django already has pinned dependencies anyway.

Hugo Osvaldo Barrera added 5 commits June 2, 2020 11:24
`smart_text` is deprecated, and will be removed in the next Django major
release. This change squelches warnings about that and makes sure we
stay future-proof.
Drop Pythons that have reached upstream EOL. Also run tests with more
recent pythons.

Hint: I'm using this in production in some large-scale apps with Django
3.0 and Python 3.8. It's been working fine.
Django 1.11 has reached its EOL, and won't work with recent (and
not-so-recent) versions of Python. Drop support for this; projects still
using older Pythons can just keep using older versions of this library.
The PNG one is too blurry on hidpi screens.
@Mogost
Copy link

Mogost commented Jun 23, 2020

@melinath @roverdotcom Could you merge these changes?

@melinath
Copy link
Contributor

melinath commented Jul 6, 2020

Sorry, I'm no longer at Rover. @philipkimmey - heads up if you want to take a look at this!

@WhyNotHugo
Copy link
Contributor Author

Ah, thanks for the heads up. If there's no longer anyone dedicated to maintaining the project, what do you think of moving this to Jazzband to be community-maintained?

@Mogost
Copy link

Mogost commented Jul 7, 2020

Totally agree for JazzBand. But we need to hear someone from the @roverdotcom.

from __future__ import print_function
from __future__ import unicode_literals


try:
import importlib
except ImportError:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In python 3 just import importlib .
There is no from django.utils import importlib in django 2.2

@philipkimmey
Copy link
Contributor

Hey @WhyNotHugo + @Mogost !

Sorry for the radio silence here - I wrote this many years ago and we don't really use it internally anymore so I think moving it to JazzBand is a great idea.

If you add me as a member there I'm happy to transfer it over and whatnot!

@Mogost
Copy link

Mogost commented Jul 7, 2020

If you add me as a member there I'm happy to transfer it over and whatnot!

JazzBand membership is open. You can join at any time. More information is available on the JazzBand site.

If the JazzBand does not accept us, I see @WhyNotHugo as a good candidate to pick up this project. As far as I can see, this fork belongs to you.

@philipkimmey
Copy link
Contributor

Whoops - sorry about that, that makes sense. I'm signing up over there now.

@WhyNotHugo
Copy link
Contributor Author

Many thanks for addressing that!
You might also need to grant PyPi permissions for future releases.

@onekiloparsec
Copy link

Any hope this great PR will be merged and released ? 🙏

@heidi-hayden
Copy link

@WhyNotHugo - did you take control of this lib?

@WhyNotHugo
Copy link
Contributor Author

@heidi-hayden nope.

I was hoping it'd be moved into jazzband, but still waiting on that.

@jkeyes
Copy link

jkeyes commented Feb 10, 2021

@philipkimmey is there a reason why this project hasn't moved to JazzBand yet? It seems a shame to let this sit idle when there appears to be people willing to maintain it. Not sure what I can contribute at this stage, but if I can help out with getting things moving let me know.

@WhyNotHugo
Copy link
Contributor Author

I've pushed django-inlinecss-redux==0.4.0.

https://github.com/WhyNotHugo/django-inlinecss/tree/v0.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants