> You mean submitting a patch upstream? Yes. I had not realized we behave differently with respect to Cython. Would it not be enough to pass whatever an hypothetical upstream version of attach produces through the preparser we use in the interactive shell? S.
* leif <not.rea...@online.de> [2016-08-26 16:23:53]: > VulK wrote: > >> and me too, this is really very annoying that %attach is broken.. > > +1 > > > > A related question: why do we implement %attach in sage rather than making a > > patch for upstream IPython? > > You mean submitting a patch upstream? > > (Otherwise repackagers won't be happy, but upstream would have to accept > it of course. I'm not sure it would be suitable, as AFAIK we use our > own Cython stuff to attach Cython files, i.e., extension modules.) > > > -leif > > > > * Frédéric Chapoton <fchapot...@gmail.com> [2016-08-26 06:01:23]: > > > >> and me too, this is really very annoying that %attach is broken.. > >> Le dimanche 14 août 2016 02:14:44 UTC+2, Travis Scrimshaw a écrit : > >> > >> I would really like to have %attach back working. > >> Best, > >> Travis > >> On Friday, August 12, 2016 at 12:50:23 PM UTC-5, Volker Braun wrote: > >> > >> Presumably attach (or, more generally, using the python inputhook) > >> doesn't work since Ipython 5 now implements its own input handling. > >> On Friday, August 12, 2016 at 2:22:51 PM UTC+2, Frédéric Chapoton > >> wrote: > >> > >> is this only me, or the recent update to ipython 5.0 has broken severel > >> things in 7.4.b0 ? > >> it seems that somebody already complained about sage_mode and %lprun > >> (see [1]https://trac.sagemath.org/ticket/21006) > >> for me, %attach does not seem to reload the files that changed > >> and using %debug doe snot quite work, because the special command r and > >> n are still mapped to numerical and R interpreter inside the ipbd > >> session > >> Frederic > >> > >> -- > >> You received this message because you are subscribed to the Google > >> Groups "sage-devel" group. > >> To unsubscribe from this group and stop receiving emails from it, send > >> an email to [2]sage-devel+unsubscr...@googlegroups.com. > >> To post to this group, send email to [3]sage-devel@googlegroups.com. > >> Visit this group at [4]https://groups.google.com/group/sage-devel. > >> For more options, visit [5]https://groups.google.com/d/optout. > >> > >> References > >> > >> 1. https://trac.sagemath.org/ticket/21006 > >> 2. mailto:sage-devel+unsubscr...@googlegroups.com > >> 3. mailto:sage-devel@googlegroups.com > >> 4. https://groups.google.com/group/sage-devel > >> 5. https://groups.google.com/d/optout > > > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
