Added a new option to avoid forcing of DEBUG setting to False

[bubenkoff]

closes #228

[bubenkoff]

@blueyed, @pelme
can you please review?

[blueyed]

I find the option name confusing, because of the double negation.

Given that, I think it might be better to make the option control the DEBUG setting. Something like --django-debug, which would default to False (current behavior) and could be also True (enable debugging from pytest), or None (do not force setting/changing it).

[landscape-bot]

Repository health decreased by 0.13% when pulling 5297b81 on no-force-debug into 1f279de on master.

• 1 new problem was found (including 0 errors and 1 code smell).
• No problems were fixed.

[blueyed]

@bubenkoff
What's your opinion on my comment / feedback?

[bubenkoff]

i agree, will change the PR

On 29/04/2015, Daniel Hahler notifications@github.com wrote:

@bubenkoff
What's your opinion on my comment / feedback?

---

Reply to this email directly or view it on GitHub:
#231 (comment)

Anatoly Bubenkov

[osantana]

👍

[pelme]

@bubenkoff Sorry for the delay, it is now merged, will hopefully put out a new release later today :)

[blueyed]

@pelme
That should not have been merged yet: #231 (comment)

[pelme]

Oops, sorry about that, I have reverted the merge in 3cd0d32.

[pelme]

Meh. github won't allow re-opening a pull request. @bubenkoff can you please create a new PR? Sorry for the mess. :(

[bubenkoff]

no problem

On Sun, Jul 26, 2015 at 8:53 PM Andreas Pelme notifications@github.com
wrote:

Meh. github won't allow re-opening a pull request. @bubenkoff
https://github.com/bubenkoff can you please create a new PR? Sorry for
the mess. :(

—
Reply to this email directly or view it on GitHub
#231 (comment)
.