Bumped Markdown version to 3.3

[smithdc1]

Markdown version 3.3 changes the whitespace of the output.

Looking at the failing test it is suited to pass on multiple versions of Markdown. However, the tests are only run against the pinned dependency. Therefore I've simplified the test to only test against this one version.

Secondly, I've also added a pytest skip mark so it skips the test 'loudly'.

Final note, and more of a question really, most of the tests here are under a class which is subclass from TestCase however, all of the tests are written pytest style. Is there a reason for this, I guess it allows categorisation of the tests?

[adamchainz]

I guess it allows categorisation of the tests?

And also the use of all of Django's TestCase features. Imo pytest with plain assert style and django TestCase classes give the best of both worlds.

[adamchainz]

Looking at the failing test it is suited to pass on multiple versions of Markdown. However, the tests are only run against the pinned dependency. Therefore I've simplified the test to only test against this one version.

The test still runs on Python 3.5 / the old markdown?

[smithdc1]

Hi Adam -- Yes, but the format is different on the slightly older version. I'll try and have a look later on but I'm thinking of making this along the lines of...

if PY == 3.5:
  do old thing
else: 
 do new thing

Or we could skip the test on Py3.5?

[adamchainz]

LGTM