Hi Dirk,
Dirk Scharff writes:
> Perhaps I should repost the remaining question under a new subject?
> I'm still not used to this ;)
The list is quite informal, but we try to stick to a
one-problem/one-thread policy -- it makes things easier.
Thanks!
--
Bastien
Hi Bastien,
thanks for pointing that out to me, I'm still new here and to org-mode in
general (and I really like it!) ;)
I'll do that in the future. While a better solution to this would be nice, I'll
not append this to this subject this time because I don't want to mess up the
topic struct
On Fri, Jul 22, 2011 at 9:55 AM, Dirk Scharff
wrote:
> Hi
>
> Am 22.07.2011 um 09:34 schrieb Rainer M Krug:
>
> For tangling: you could put from __future__ imports into the :shebang and
> use padline ":padline no", i.e.:
>
> #+source: the_test
> #+begin_src python :var x=3 :tangle test.py :resul
Hi
Am 22.07.2011 um 09:34 schrieb Rainer M Krug:
> For tangling: you could put from __future__ imports into the :shebang and
> use padline ":padline no", i.e.:
>
> #+source: the_test
> #+begin_src python :var x=3 :tangle test.py :results output :shebang from
> __future__ imports :padline no
On Fri, Jul 22, 2011 at 9:22 AM, Dirk Scharff
wrote:
> Hi
>
> i just noticed that variables are assigned in the top of the exported code.
> That can be problematic in some situations:
>
> #+source: the_test
> #+begin_src python :var x=3 :tangle test.py :results output
> from __future__ import divi
Hi
i just noticed that variables are assigned in the top of the exported code.
That can be problematic in some situations:
#+source: the_test
#+begin_src python :var x=3 :tangle test.py :results output
from __future__ import division
print x
#+end_src
tangling results in:
x=3
from __future__
