Make inline comments handling optional and disabled by default

[sergeyklay]

Disabled inline comments handling (that was introduced in #475) by default due to potential side effects. While the feature itself is useful, the project's philosophy dictates that it should not be enabled by default for all users.

Closes #499

[coveralls]

coverage: 92.268% (+0.05%) from 92.215% when pulling 35933b6 on fix/issue-499 into 7b5d7f9 on develop.

[lvanderree]

👍 this is exactly what I had in mind after hearing about the issues: Add a feature flag to enable/disable it

[ognjenk]

Do you maybe know when this fix might be pushed into release?

[sergeyklay]

Do you maybe know when this fix might be pushed into release?

We'll try to release next week.

[simonkern]

Sorry for bringing this issue up again, but any update on when this will be released? I've yet encountered another instance of corrupted session data because the SECRET_KEY was interpreted differently for uWSGI and gunicorn / uvicorn.

[jiayouzl]

Do you maybe know when this fix might be pushed into release?

We'll try to release next week.

Has the new version not been released yet? I have also encountered this problem.

I found that this issue only occurs in Ubuntu. The "#" symbol in the .env file is not affected on macOS system. What's going on?

[dklotz]

We'll try to release next week.

@sergeyklay Sorry to sound a bit pushy, but any updates on when this release will happen? This seems to affect a lot of people (cf #519), especially with SECRET_KEY and the related session data corruption.

[jiayouzl]

We'll try to release next week.

@sergeyklay Sorry to sound a bit pushy, but any updates on when this release will happen? This seems to affect a lot of people (cf #519), especially with SECRET_KEY and the related session data corruption.

I have been waiting for a long time too. In fact, they have already fixed it in the branch but just haven't released it. 😀

[dklotz]

I have been waiting for a long time too. In fact, they have already fixed it in the branch but just haven't released it. 😀

Yes, I also noticed that. For us the workaround for now is just using the version from the git develop branch in our pyproject.toml:

[tool.poetry.dependencies]
...
django-environ = { git = "https://github.com/joke2k/django-environ.git", rev = "a1113e41" } # TODO: switch to release once this bug is fixed: https://github.com/joke2k/django-environ/issues/519