On 2/15/20 9:33 PM, Kwankyu Lee wrote:
>
> It would also be mildly confusing to allow both of these
>
> from sage.coding.punctured_code import PuncturedCode
> PuncturedCode(...)
>
> and
>
> codes.punctured_code(...)
>
> So your suggestion would imply that we should discourage user
On Sunday, February 16, 2020 at 10:10:11 AM UTC+9, Michael Orlitzky wrote:
>
> On 2/14/20 7:55 PM, Michael Orlitzky wrote:
> >
> > But... is that the distinction that we want to make? I'm skeptical that
> > the person who wrote that paragraph in the developer's guide had the
> > 1995 definition
On 2/14/20 7:55 PM, Michael Orlitzky wrote:
>
> But... is that the distinction that we want to make? I'm skeptical that
> the person who wrote that paragraph in the developer's guide had the
> 1995 definition of "factory" in mind. I actually like this convention,
> but it's a bit subtle.
>
...an
I've proposed a fix (well, no notebook() on Py3 Sage) for this on
https://trac.sagemath.org/ticket/29195
On Thu, Feb 13, 2020 at 7:18 PM Dima Pasechnik wrote:
>
> in Python 3-based sage this won't work.
>
> we need to fix this..
>
> You can use Jupyter-based notebook, but then you launch it at Sa
I have made a mistake in the original post.
EDIT: this reference was wrong the original post
--- by M. C. Er, The Computer Journal, Vol. 31, 1988, 283-284,
CORRECTION: the reference for the Haskell source should read
+++ by Brent Yorgey,The Monad.Reader Issue 8 , September 10, 2007
Sorry about
I made a mistake in the reference.
EDIT: this reference was wrong the original post
--- by M. C. Er, The Computer Journal, Vol. 31, 1988, 283-284,
CORRECTION: the reference for the Haskell source should read
+++ by Brent Yorgey and Conrad Parker,The Monad.Reader Issue 8 , September
10, 2007
Sor
