I would humbly like to suggest icalendar drop support for Python 2.6.
The last release of Python 2.6 was 2013-10-29. It is no longer receiving
security or bug fixes.
https://www.python.org/dev/peps/pep-0361/
The pip project itself has decided to drop support for 2.6. At the
beginning of the year, their numbers estimated that Python 2.6 accounts
for ~2% of their downloads.
https://github.com/pypa/pip/pull/4343
For projects that still use Python 2.6, they can continue to pip install
an older version.
I've tried my best to remove as much 2.6 specific code as I can,
including the 'Programming Language :: Python :: 2.6' trove classifier
from setup.py. I've also removed Travis CI testing, which should result
in slightly faster testing and fewer wasted resources.
Changed:
* Update documented Python support and trove classifiers
* Update Travis test matrix and tox test matrix
* Use set literals (and more literals in general)
* Use dict comprehension
* Remove dependencies on ordereddict and unittest2
* Remove u string prefix, use more modern unicode literals instead
The fix for #197 makes the test data used for testing the error
messages for broken properties (which was valid data) work with
icalendar, we therefor need a new test with actually invalid data.
Some parameter values (e.g., BASE64 encoded binary data often ends with
one or two equal signs) may contain an equal sign (`=`). The current
implementation splits key-value pairs at all equal signs, which leads to
errors. Especially icalendar files generated by Apple's software often
feature BASE64 encoded binary data in parameter values.
This patch introduces a new parameter `maxsplit` to
icalendar.parser.q_split() which works similar as python's
string.split(sep, maxsplit) which we then use to split parameter
key-value pairs only at the first equal sign.
This patch fixes#197.
Now not accepting unsecaped new line characters in a content line.
When folding line - preserving space at the end, if present.
Modified the tests accordingly.