Re: (9.2) Noweb blocks not expanded in Python blocks : it should be a bug...

[Emmanuel Charpentier <emm.charpentier@free.fr>]

as of today's (20190118) org-plus-contrib, this seems fixed. Quick
check :

===================================================================
# Noweb syntax check

#+property: header-args:python :session
#+property: header-args:sage :session

#+name: A
#+begin_src sage
L.append(i)
#+end_src

#+name: B
#+begin_src sage :noweb yes :exports both
  L=[]
  for i in range(1,6):
      <<A>>
  L
#+end_src

#+name: C
#+begin_src python
L.append(i)
#+end_src

#+name: D
#+begin_src python :noweb yes :exports both
  L=[]
  for i in range(1,6):
      <<C>>
  L
#+end_src
===================================================================

Thanks a lot !

--
Emmanuel Charpentier

Le lundi 04 février 2019 à 18:03 +0100, Nicolas Goaziou a écrit :
> Hello,
> 
> Robert Pluim <rpluim@gmail.com> writes:
> 
> > John Kitchin <jkitchin@andrew.cmu.edu> writes:
> > 
> > > #+RESULTS:
> > > : <<\([^
> > > : ].+?[^ ]\|[^
> > > : ]\)>>
> > 
> > That regex looks malformed, and will only match strings with 1 or 3
> > or
> > more characters between << and >>. If someone knows what itʼs
> > supposed
> > to be matching we can fix it. eg it looks like it wants to allow
> > 
> > <<ab
> > 
> > Is that something that should be accepted?
> 
> I fixed the regexp. Thank you.
> 
> Regards,
>