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

Support for Python 3 and Django 1.9+ (plus Tox) #26

Closed

Conversation

PiDelport
Copy link
Collaborator

This makes the test suite pass on 2.7 + 3.5, and Django 1.8 – 1.10.

This also adds a Tox configuration that will test all combinations of the above.

This ensures that Django is actually an installation requirement, and
allows Tox to run the tests with varying versions of Django more easily.
Users of this library may be running other versions of it.
This should get the test suite passing on Python 3 / Django 1.8.
This means that the output is no longer left unescaped by default, and
an explicit mark_safe() is required to leave the seo_js_head tag's HTML
markup intact in Django 1.9+.

Further reading:

https://www.djangoproject.com/weblog/2015/jun/29/simple_tag-security-
advisory/

https://docs.djangoproject.com/en/stable/releases/1.9/#simple-tag-
conditional-escape-fix
Django 1.10 no longer supports the old TEMPLATE_* settings.
This was referenced Oct 5, 2016
@Luis-Palacios
Copy link

What is stopping this from being merge? I need python 3 and django 1.8 support :(

@Anton-Shutik
Copy link

@skoczen Whats up on this ?
I need django 1.10 support and would add PR django 1.11 support, but I see that nobody going to merge pull requests.
This project will die if not supported. If you have no time, can you add somebody from PR authors as collaborators ?

@thoop
Copy link

thoop commented Apr 12, 2017

Let me see if I can get in touch with someone. Sorry for the delay here!

@skoczen
Copy link
Owner

skoczen commented Apr 12, 2017

Hey @Anton-Shutik and @thoop @pjdelport @LRPalacios thanks for your patience - the delay has been moving to a new country, switching jobs, and basically all of life being upside down. I haven't had time to test any of the proposed changes, but if I can get a thumbs up from folks who have tested this and see that it's working, I'll just do a release blind to unblock folks.

Please let me know, and thanks for hanging in there!

@jjwon0
Copy link

jjwon0 commented Feb 15, 2018

Wondering if this is still planned to go in. Cheers!

@pcraciunoiu
Copy link
Collaborator

@skoczen if you're up for it, you can add another collaborator (me, or anyone here who's up for it). Basically:

  1. create a GitHub organization or grant access to this repo (pcraciunoiu for me)
  2. also on pypi (embrangler for me), can do that probably here: https://pypi.org/manage/project/django-seo-js/collaboration/

With that someone else can merge PRs and create releases. I added some updates in a new PR since it didn't work for me on Django 2, and pulled in changes from other forks that I found useful: #30.

@skoczen
Copy link
Owner

skoczen commented May 4, 2018

Quick reply - definitely up to add a collaborator. Slammed right now, but will hopefully get this done next week! Thanks for your patience!

@mkaliberda
Copy link

also, please add .base to import
from .base import SEOBackendBase, RequestsBasedBackend
from .base import SEOBackendBase

@derek-adair
Copy link

@skoczen I'm available and looking to take on more open source project management experience.

I'll contact you directly to ensure you see this ;)

@pcraciunoiu
Copy link
Collaborator

I'm up to be added as a reviewer/collaborator as well.

I think prerender released some updates for Google's changes in July, not sure if we need anything there but @derek-adair if you have time, take a look! I contacted them since I set it up for a client, and will follow up if they suggest anything.

Google is moving away from crawling escaped_fragment URLs and some users have reported this causing issues with their SEO.
You can find information on Google's change and how to upgrade or add Googlebot's user agent to your middleware here:
https://prerender.io/documentation/google-support

@PiDelport
Copy link
Collaborator Author

This project may also be a good candidate for Jazzband?

@derek-adair
Copy link

derek-adair commented Aug 30, 2018

WTF jazzband is awsome!! I'd love to get involved.

I ended up having to take over burntsushi/nflgame because of burnout. Currently convincing the author to let me take over the pypi namespace but he's understandibly reluctant so i've taken it upon myself to make a redux fork

@guykogel
Copy link

@skoczen any updates here?

@skoczen
Copy link
Owner

skoczen commented Feb 6, 2019

Update - things are moving forward without me being in the way. Please see #32 for our next steps in this project, and thank you so much for your contributions, and for your patience. :)

Ping: @guykogel @derek-adair @pjdelport @pcraciunoiu @mkaliberda @jjwon0 @thoop @Anton-Shutik @Luis-Palacios

@pcraciunoiu
Copy link
Collaborator

If anyone wants to update this, I'd be happy to review and help merge.

@PiDelport
Copy link
Collaborator Author

@pcraciunoiu: I reviewed, and it looks like PR #30 supersedes this. Thanks!

@PiDelport PiDelport closed this Mar 5, 2019
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.