Comment not parsed

[Marrin]

Maybe this is connected to issue #67 but it's worse than just having the wrong node type, because it breaks the round trip promise:

In [27]: source = '''#!/usr/bin/env python
# coding: utf8
'''

In [28]: red = RedBaron(source)

In [29]: red
Out[29]: 
0   '#!/usr/bin/env python\n'
1   '#!/usr/bin/env python\n'


In [30]: red[0]
Out[30]: '#!/usr/bin/env python\n'

In [31]: red[1]
Out[31]: '#!/usr/bin/env python\n'

In [32]: red.dumps()
Out[32]: '#!/usr/bin/env python\n\n'

The second node seemingly repeats the first comment but when rendered back to source even that is gone, as is the coding comment. Tested with Python 2.7, baron 0.6.2, and redbaron 0.6.1

[ibizaman]

Yes, comment handling is pretty brittle at the moment. Thanks for reporting!

[gtors]

It's bug of IPython shell: proof
In native python shell the bug is not reproduced.

[b5y]

@gtors Interesting. I know that IPython have some bugs. One of them with StringIO I detected few months ago (it was not new version of IPython, but it does not matter).

I have used python 2.7 and RedBaron had bug with comments. Did you try with Python 2.7?

[gtors]

@b5y Python 2.7 shell also works fine: asciinema
p.s.: for py3 I use patched version of baron, so, result of calling parse in py2 is a bit different.

[ibizaman]

I can unfortunately confirm it's an iPython problem:

@gtors do you have an idea of what the problem is?
@b5y @Marrin latest baron has (one of) the comment issue fixed, see PyCQA/baron#88

[gtors]

@ibizaman ipython/ipython#9919

[Marrin]

I've revisited this with current versions of IPython and the involved libraries and the problem is fixed/gone. Given that it was a bug in IPythone anyway, I think this should be closed.