Re-fix ImproperlyConfigured error when calling from CLI in Django 1.8 (#183)#255
Open
abbottc wants to merge 1 commit intosyrusakbary:masterfrom
abbottc:django18_fix
Open
Re-fix ImproperlyConfigured error when calling from CLI in Django 1.8 (#183)#255abbottc wants to merge 1 commit intosyrusakbary:masterfrom abbottc:django18_fix
abbottc wants to merge 1 commit intosyrusakbary:masterfrom
abbottc:django18_fix
Conversation
|
Since there are no updates to pyjade and its successor recently was deleted from pypi, I took the liberty to revive it: https://github.com/kakulukia/pypugjs Version 5.0.1 has fixed the incompatibility with recent Django versions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
March 25th of last year, issue #183 was created and a fix was merged for it. Then on Nov 7th of last year, #215 was merged. Unfortunately, that merge removed the code which fixed #183. I ran into the problem described in #183 and through troubleshooting it, I saw the history I just described and verified that the issue was resolved by re-adding the code. This pull request re-adds the code along with a comment as to why it's there for some extra safety.