[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] babel evaluation of python and utf-8
|
From: |
Daniel Clemente |
|
Subject: |
Re: [O] babel evaluation of python and utf-8 |
|
Date: |
Tue, 08 Jul 2014 11:57:19 +0700 |
|
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.4.50 (x86_64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
El Fri, 04 Jul 2014 16:08:10 +0200 Alan Schmitt va escriure:
>
> On 2014-06-26 18:07, Daniel Clemente <address@hidden> writes:
>
> >>
> >> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
> >> print(u'é')
> >> #+END_SRC
> >>
> >
> > I also see the same problem here. Even if you include # -*- coding: utf-8
> > -*- as the first line.
> >
> > Shouldn't org-babel already be using utf-8 instead of ASCII for
> > input/output?
> >
> > By the way, with Python3 it doesn't happen since it doesn't need the
> > coding:utf-8 declaration anymore.
>
> Should this be considered a bug, or do we require python 3 for such
> things?
>
I think if the user writes the # -*- coding: utf-8 -*- line, org-mode should
pass it. With that, all Pythons (Python2, Python3) work well, so I wouldn't say
there's a bug in Python. It would be in org-mode.