Version 0.8.0 generates "Invalid line" error on blank lines in file

[KenWhitesell]

A blank line in an env file causes Django's manage.py to show "Invalid line" messages. This occurs even if no sub-command is specified.

An error is also thrown on a line beginning with an octothorpe ("#") - something that we use to comment those files.

The Usage docs don't specifically state that these are legal lines. However, the example further down on that page uses them within the example.

[devel-pa]

Looks like the feature that displays invalid lines, a nice one, doesn't take in account the fact that there are also empty or commented lines. An invalid line is skipped anyway, so those lines where treated as invalid, now just annoyingly shown.

https://github.com/joke2k/django-environ/blob/main/environ/environ.py#L825

[KenWhitesell]

Is there an "official" opinion as to whether those types of lines are -

1. Officially considered "invalid" and therefore should be logged?
2. Officially "invalid" but not logged (conditional test added before line 825)?
3. Officially "valid", and should be part of the regex identifying valid lines?
4. Filtered out (ignored) before the regex test at line 813?

[sergeyklay]

This was a feature that got into the release without proper attention. I'll fix this in the next release.

[sergeyklay]

Fixed in develop branch. I'll release a hotfix ASAP. Thank you for reporting.

[sergeyklay]

Just released v0.8.1:

• https://github.com/joke2k/django-environ/releases/tag/v0.8.1
• https://pypi.org/project/django-environ/0.8.1