should merging of #183 necessary?

[yuex]

Right, according to pep8, we need #<space> instead of #. But this kind of behavior can be implemented by let g:NERDSpaceDelims = 1. Actually, isn't it necessary to add a space between the comment delimiter of any language to make it clean? The requirement of pep8 should not make python a special case. Or at least the committer should take into account of g:NERDSpaceDelims. Someone argues that #183 makes it simpler for python commenting from the start. But before the merging I just need to config

let g:NERDSpaceDelims = 1

now I have to config

let g:NERDSpaceDelims = 1
let g:NERDCustomDelimiters = {'python': {'left': '#'}}

besides two hours wasted on locating the reason why <Leader>cc only cause comments in python two spaces instead of one.

[cherrot]

Agree.
Now I have to config for python specifically. It is annoying, really.

[ryneeverett]

Is making NERDSpaceDelims=1 the default a potential option? That would be pep8-compliant by default and avoid making python a special case. And as pointed out above:

Actually, isn't it necessary to add a space between the comment delimiter of any language to make it clean?

[ryneeverett]

On a somewhat tangential note, the current "fix" doesn't seem to even address pep8 block requirements:

Block comments generally apply to some (or all) code that follows them, and are indented to the same level as that code. Each line of a block comment starts with a # and a single space (unless it is indented text inside the comment).

Emphasis mine. The current implementation yields:

# some_block = {
    # 'a': 1,
    # 'b': 2}

in which pep8/pycodestyle tool correctly identifies "unexpected indentation", rather than:

# some_block = {
#     'a': 1,
#     'b': 2}

[kalq]

I think you can meet Pep8 requirements with:

let NERDDefaultAlign="left"

Put it inside .vim/after/ftplugin/python.vim to avoid changing the setting for other filetypes.