[sage-devel] Re: VOTE: move Sage development to Github

+1 GitHub On Sunday, October 2, 2022 at 6:51:39 PM UTC+2 kesha...@gmail.com wrote: > +1 for GitHub (hi folks 🙂) > > -Keshav > > On Wednesday, September 21, 2022 at 10:23:36 AM UTC-7 David Roe wrote: > >> Dear Sage developers, >> Following extensive discussion, both recently >>

Re: [sage-devel] any([magma(True),magma(True)]) produces stack overflow

gt; > It was reported fixed for 9.5, and Volker’s release message for 9.5.beta6 > indicates it was included then. And it does not fail for sage 9.5 on my > system. > > Simon may let us know what config he’s using. > > Justin > > > On Fri, Feb 18, 2022 at 2:58 PM '

[sage-devel] any([magma(True),magma(True)]) produces stack overflow

``` sage: any([magma(True),magma(True)]) Fatal Python error: _Py_CheckRecursiveCall: Cannot recover from stack overflow. Python runtime s

[sage-devel] Re: Outdated instructions in "git the hard way"

of doing a series of commands that I simply don't manage to memorise. Best regards, Simon -- 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+un

[sage-devel] Re: Help needed with adding user packages as optional/experimental packages

Most of its latest releases were triggered by changes in Sage. Best regards, Simon -- 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+unsub

[sage-devel] [SageTerminalApp] ERROR | Failed to create history session

When working with multiple terminals I frequently get the following Error. Usually when the other terminal is busy. [SageTerminalApp] ERROR | Failed to create history session in /home/simon/. sage/ipython-5.0.0/profile_default/history.sqlite. History will not be saved .Traceback (most recent

[sage-devel] Re: Rounding in Sage

Hi Samuel, thank you for the interesting sources! Best regards, Simon On 2020-04-08, Samuel Lelievre wrote: > About Sage and floating-point numbers, if I remember correctly, > > - IEEE 754 is not a complete specification, some details are left > up to the implementation and th

[sage-devel] Re: Rounding in Sage

959590107546, -52) Nice, I didn't know about that method. Thank you for the hint! Simon -- 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+uns

[sage-devel] Re: Rounding in Sage

On 2020-04-07, Thierry wrote: > An appropriate place seems to be : https://ask.sagemath.org/questions/ I will never prefer ask.sagemath over sage-support. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop re

[sage-devel] Rounding in Sage

alf to 0, round half away from 0, round half to +infty, round half to -infty, round half to even, round half to odd, round half alternatingly to 0 and away from 0, do the rounding in RR, ...). Is there such function in Sage? Otherwise I would just write a custom function for my course. Best reg

[sage-devel] Re: Inherit Method but keep Documentation?

Type sage: class FlexibleDocMethodType(MethodType): : pass : ... TypeError: type 'method' is not an acceptable base type Best regards, Simon On 2020-03-18, Michael Jung wrote: > Dear developers, > to reduce redundancies in the SageManifolds code, we plan to in

[sage-devel] Re: Inherit Method but keep Documentation?

Hi! On 2020-03-19, John H Palmieri wrote: > What about > > my_method = Mother.my_method > my_method.__doc__ = "new docstring" > > > Does that do what you want? Probably not. Wouldn't that be the same as Mother.my_method.__doc__ = "new docstring"

[sage-devel] Re: yanking sage doctests in vim

[4 0 1] sage: type(M) # optional: meataxe eventually became sage: M = MatrixSpace(GF(25,'z'),2,3)([1,2,3,4,5,6]) : print(M) : type(M) # optional: meataxe : [1 2 3] [4 0 1] in Sage command line after pasting. In spite of th

[sage-devel] Re: yanking sage doctests in vim

mand line and hit -insert (which usually inserts what was previously copied), nothing happens (resp. some text was inserted that I have copied previously). This is with vim version 8.2.343 What am I doing wrong? Best regards, Simon -- You received this message because you are subscribed to the G

[sage-devel] Re: yanking sage doctests in vim

lly stripped, which is of course useful because it is Sage's job to compute that output? - How is vim involved in my interaction with Sage? Do you mean the following: Open some file in vim that contains doctests, mark a doctest in vim, then go to the Sage command linel and paste what you'v

[sage-devel] Re: Tip: easy input of math/unicode symbols

#x27;t reinvent the wheel (because it makes use of existing functionality), and for those cases that still don't work the user can provide the latex name explicitly. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To un

[sage-devel] Re: Tip: easy input of math/unicode symbols

On 2020-02-21, Simon King wrote: > Hi Emmanuel, > > On 2020-02-21, Emmanuel Charpentier wrote: >> sage: latex(λ^2) >> λ^{2} > > Couldn't we modify the latex() function, by exploiting > IPython.core.completer.reverse_latex_symbol, to automatically translat

[sage-devel] Re: Tip: easy input of math/unicode symbols

Hi Emmanuel, On 2020-02-21, Emmanuel Charpentier wrote: > sage: latex(λ^2) > λ^{2} Couldn't we modify the latex() function, by exploiting IPython.core.completer.reverse_latex_symbol, to automatically translate all unicode symbols that aren't understood by pdflatex? Best regards

[sage-devel] Re: Poll: make giacpy_sage a standard package

a (standard) spkg. Best regards, Simon -- 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 view this discus

[sage-devel] Re: Poll: make giacpy_sage a standard package

Giac is standard, it totally makes sense to me to make its C-bindings standard, too. So, +1 from me. Best regards, Simon -- 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 a

[sage-devel] Re: Poll: make giacpy_sage a standard package

Hi Samuel, On 2020-02-03, Samuel Lelievre wrote: > Please vote for making giacpy_sage a standard package. Could you elaborate what giacpy is about, i.e., what functionality would it add to SageMath resp. improve in SageMath? That question isn't addressed on the ticket yet. Best regard

[sage-devel] Re: Unable to build sage after git trac config

s fine, too. But please do not remove the customised scripts or their documentation. Best regards, Simon -- 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 ema

[sage-devel] Re: Unable to build sage after git trac config

Hi Eric, On 2020-01-30, Eric Gourgoulhon wrote: > I would even vote for removing the git-trac section from the developer > manual. -1 I do use "git trac". Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel&q

[sage-devel] Re: Python 2->3 incompatibility in unpickling

Hi Nils, yes, that's exactly the same problem! Thank you for reminding me. I've totally forgotten how the "correct" encoding was called. Best regards, Simon On 2020-01-22, Nils Bruin wrote: > On Wednesday, January 22, 2020 at 1:35:16 PM UTC-8, Simon King wrote: &

[sage-devel] Python 2->3 incompatibility in unpickling

string.str_to_bytes(s) b'\xc2\x80\x1f' Best regards, Simon -- 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...@googlegrou

[sage-devel] Re: Problem reading this list with slrn

Dear Dima, Indeed it now works. I didn't change anything, just tried again. So, problem solved... Thank you! Simon -- 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

Re: [sage-devel] Problem reading this list with slrn

indeed it mentions news.gmane.io instead of news.gmane.org. So, what else can I do? Best regards, Simon -- 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] Problem reading this list with slrn

mething about it? Or is news.gmane.org simply dead? Best regards, Simon -- 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...@

[sage-devel] Re: drop python2 compatibility in 9.1 ?

e developers will be small: If (on top of bug fixes) there would be new code in v9.1, then making it work with py-2 would basically involve some "from __future__ import", isn't it? Best regards, Simon -- You received this message because you are subscribed to the Google Groups &quo

[sage-devel] Re: Coercion between quadratic fields fails (by default)

roots() [(-sqrt(3), 1), (sqrt(3), 1), (-I*sqrt(15), 1), (-I*sqrt(3), 1), (I*sqrt(3), 1), (I*sqrt(15), 1)] That's actually quite nice! So, it would be a good default -- if performance wouldn't be a problem. Anyway, thank you for pointing to this option, because I wasn't awa

[sage-devel] Re: Package installation/uninstallation confusion

Dear Erik, On 2019-11-12, E. Madison Bray wrote: > On Fri, Nov 8, 2019 at 11:06 PM Simon King wrote: >> While we are at it: Currently, for building the package's documentation, >> I use "$MAKE html" followed by some "cp -r" to copy the re

[sage-devel] Re: Package installation/uninstallation confusion

owed by some "cp -r" to copy the resulting html files to $SAGE_SHARE/doc/p_group_cohomology. I guess this needs to be fixed (in the sense of "rather use sdh_*) as well I opened #28711 for it. Best regards, Simon -- You received this message because you are subscribed to the Google Gr

[sage-devel] Re: Package installation/uninstallation confusion

ile, then there would be no need to split the package. I.e., the question is whether "sdh_pip_install" will override the json file created by "sdh_make_install", or whether it will append to it. Best regards, Simon -- You received this message because you are subscribed to th

[sage-devel] Re: Package installation/uninstallation confusion

Hi John, thank you! So, I'll try sdh_make_install (sdh_install just copies some files), keep using sdh_pip_install, and check what jason file results. Best regards, Simon On 2019-11-07, John H Palmieri wrote: > These shell functions are defined and documented in > SAGE_ROOT/bui

[sage-devel] Re: Package installation/uninstallation confusion

ckages use sdh_make_install (note the difference: What got broken apparently was sdh_make install with a blank space) than sdh_install. Can you point me to man pages, where sdh_install versus sdh_make_install is discussed? Best regards, Simon -- You received this message because you are subscribe

[sage-devel] Re: Package installation/uninstallation confusion

s the autotoolized c-library part of p_group_cohomology-3.3 Advantage: "make p_group_cohomology" would also install the dependency, hence, both packages get installed. And both packages can also be un-installed, I suppose. Disadvantage: The only purpose of modular_resolution-1.0 wou

[sage-devel] Re: Package installation/uninstallation confusion

s to spkg-install. Can someone give me a pointer on what should be done in that script and what tools (sdh_*) are available for it? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and st

[sage-devel] Re: Gram-Schmidt Procedure for Symbolic Ring

599771853409352442745266/2780802606066896232581239559281727773240004199722661 > sage: bool(pi == q) > True Nice! Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emai

[sage-devel] Re: Gram-Schmidt Procedure for Symbolic Ring

m. > > While I agree in principle with Simon, actually *doing* it isn't easy. Indeed. I had teaching in mind when I suggested to have an option to force "numerically evil" methods, as the students tend to not believe that a method they learned in the first year can be problem

[sage-devel] Re: Gram-Schmidt Procedure for Symbolic Ring

On 2019-10-24, Michael Jung wrote: > Do you have an example where SR fails to be exact? One can convert a float to SR. The result is in SR, but still behaves like a float: sage: a = SR(2.)^(1/500) sage: a^500 2.05 sage: a.parent() Symbolic Ring Best regards, Simon --

[sage-devel] Re: Gram-Schmidt Procedure for Symbolic Ring

ay, what does "exact" actually mean? It means that arithmetics is not affected by rounding/approximations. And some methods (apparently Gram-Schmidt is one of them) is only "safe" when no rounding occurs. That said, I'd appreciate to add an option that forces such methods

[sage-devel] Re: quadratic forms signature_vector() gives different results for real cyclotomics and for reals

A quadratic form is a map F^n ---> F. The signature is supposed to be independent of the choice of basis. So the number of positve/negative eigenvalues makes sense only for F = the reals. For instance in the complex numbers you can always find an orthogonal basis with gram matrix diag(1,,1,

[sage-devel] Re: quadratic forms signature_vector() gives different results for real cyclotomics and for reals

/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0, : 0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2]) sage: Q.signature_vector() should either raise a value error, or be called signature_vectors() and return a dictionary of real places and signature vectors. Best, Simon On Friday

[sage-devel] Re: Question about deprecation warnings: when do they appear in doctests vs. real life?

in > a function they've written. I don't like that idea. If they write code, I suppose many people test their code in an interactive session while writing it. So, it would be fair to show them during the interactive session that the code they're about to write is deprecated.

[sage-devel] Re: How to recover from total git screwup?

On 2019-10-02, Kwankyu Lee wrote: > Hera:sage-dev$ g version > git version 2.23.0 $ git version git version 2.7.4 May that be the problem, then? In any case, git checkout -f did work, and apparently did no harm. So, I'm back at work... Best regards, Simon -- You received t

[sage-devel] Re: How to recover from total git screwup?

On 2019-09-28, Simon King wrote: > I wonder what's different. I am still reluctant to do "git checkout -f >", but perhaps that would be my best bet. I tried, and it seemed to work. However, someone who knows about git (i.e., not I) should report the bug that git allows dele

[sage-devel] Re: How to recover from total git screwup?

you can switch branches. Aborting I wonder what's different. I am still reluctant to do "git checkout -f ", but perhaps that would be my best bet. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: How to recover from total git screwup?

t is still available in my py2 worktree. That's why I thought "git checkout -f develop" in the py3 worktree might help. But perhaps after that I'd need to rebuild Sage from scratch, too? Anyway, before trying a forced operation: Would it potentially create even more mess? Best

[sage-devel] Re: How to recover from total git screwup?

On 2019-09-27, Simon King wrote: > Indeed, all files in the Sage tree are untracked, in the py3 worktree. > And that's why "git checkout develop" won't work (it tells me to commit > are stash first). > > Can you please tell me how to recover from that mess? Pe

[sage-devel] How to recover from total git screwup?

s in the Sage tree are untracked, in the py3 worktree. And that's why "git checkout develop" won't work (it tells me to commit are stash first). Can you please tell me how to recover from that mess? Best regards, Simon -- You received this message because you are subscri

[sage-devel] NEWOBJ isn't a type object

class sage: isinstance(_, type) True Best regards, Simon -- 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 view

[sage-devel] Re: Coexistence of py2 and py3

lace, a pickle of a dictionary was unpickled apparently as a string, and sometimes was identical to . But not much else. Anyway, first tests seem to indicate that the problems vanish when changing setup.py so that creation of .c files takes place in different folders for different python versions.

[sage-devel] Re: Coexistence of py2 and py3

for py2 and what code for py3. Hence, IMHO it is clearly a bug that the .c files are not by default created in a path that depends on the language level. But I don't know where that bug should be reported. Best regards, Simon -- You received this message because you are subscribed to the

[sage-devel] Re: Coexistence of py2 and py3

. in build/c_files-3.7, whereas (as before) the .so files are in build/lib.linux-x86_64-2.7 resp. ... -3.7. I will see if this is enough to solve the problem. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubs

[sage-devel] Coexistence of py2 and py3

rch didn't tell me how to prescribe a different directory for the .c files (resp. the solutions I found, such as "python setup.py build --build-lib " didn't seem to work). Can you tell me how to prescribe a folder for the .c files? Best regards, Simon -- You received this me

[sage-devel] Recommended way to implement division for RingElement

ke x/y NOT work (and fail with a TypeError)? In the above situation, is it recommended to override double underscore __div__? Then what about Py3? Would it then be needed to override __div__, __truediv__ and __floordiv__? Best regards, Simon -- You received this message because you are subscri

[sage-devel] Re: The opportunity of Python 3 migration

n functions/methods will more often return an iterator instead of a list/tuple, what is the "cdef" type of an iterator? I.e., how can one tell Cython that a particular object is an iterator, so that Cython can produce faster code for it? Best regards, Simon -- You received this mes

[sage-devel] Using travis-ci on Sage with both py2 and py3

, Simon -- 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 view this discussion on the web visit https://groups.go

[sage-devel] Re: Unpickling problem (backwards incompatibility) in Python 3

PS: On 2019-09-03, Simon King wrote: > - Without `encoding='bytes'`, Python-3 can in general not unpickle any > pickle created with Python-2 that contains strings. Stated differently: Ostensibly, Python-2 str corresponds to Python-3 bytes, and Python-2 unicode corresponds to P

[sage-devel] Re: Unpickling problem (backwards incompatibility) in Python 3

Hi! On 2019-09-02, Simon King wrote: > The problem apparently boils down to the following: > - Pickle the string '\x80\x1f' in Python-2 > - Try to load that pickle in Python-3 (it fails). > > Bummer! Nils Bruin pointed me to https://stackoverflow.com/questions/28218

[sage-devel] Re: Unpickling problem (backwards incompatibility) in Python 3

On Monday, September 2, 2019 at 6:22:24 PM UTC+2, Simon King wrote: > > Also, if I understand the error message "UnicodeDecodeError: 'ascii' > codec can't decode byte 0x80 in position 0: ordinal not in range(128)" > correctly, it is an error in unpickling

[sage-devel] Re: Unpickling problem (backwards incompatibility) in Python 3

I understand the error message "UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in range(128)" correctly, it is an error in unpickling a string. And this, I believe, can and must be totally absolutely backwards compatible. Cheers, Simon -- You

[sage-devel] Re: Unpickling problem (backwards incompatibility) in Python 3

On 2019-09-02, Simon King wrote: > Strangely, when I read the pickle as a string >open('path/to/file.sobj').read() > then it fails with a (different?) UnicodeError in Python-3. That's not the problem. However, I am not able to track down the problem myself. So, I

[sage-devel] Unpickling problem (backwards incompatibility) in Python 3

he details (namely the pickle and the steps to read it in Python-2) can be found in https://trac.sagemath.org/ticket/28414#comment:36 Can some expert please tell me how to unpickle the pickle in Python-3? Best regards, Simon -- You received this message because you are subscribed to the Google Gro

[sage-devel] Re: Wrong python in Sage shell?

ge-sh) king@klap:~$ which python3 /home/king/Sage/git/py3/local/bin/python3 Best regards, Simon -- 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+un

[sage-devel] Wrong python in Sage shell?

regards, Simon -- 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 view this discussion on the web vi

[sage-devel] Re: inconsistency in computation of differential of a map between manifolds

Hi Eric, On 2019-08-27, Eric Gourgoulhon wrote: > To avoid such mistake, you can run set_inverse() with the option > verbose=True. Then the provided inverse transform is checked. Is the option really called "verbose=True"? Not "check=True", like in most other c

[sage-devel] Re: slowness in copy of integer sparse matrices

Hi all, did someone open a ticket for that issue? Best regards, Simon On 2019-08-24, Nils Bruin wrote: > It seems to be spending a lot of time in cython code, so "%crun" might give > the best idea. This is part of the profile obtained by running the "copy" > c

[sage-devel] Re: doctest a single function or class

would be used once the piece of code is published. I.e., I cannot see how that feature would be useful in the Sage test suites, but I see potential use in development. Is that the use case you had in mind? Best regards, Simon On 2019-07-09, TB wrote: > Dear list, > > Is there a way to test

[sage-devel] Re: save/loads and the pickle jar

absolutely needed for a project that isn't dead!) while still being able to read data that you have stored with your old code? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and s

[sage-devel] Re: Possible to use current Sage version in travis-ci?

supported. Indeed it seems that "docker pull sagemath/sagemath-dev:develop" works (note: sagemath-dev:develop, not sagemath:develop). Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from thi

[sage-devel] Re: Possible to use current Sage version in travis-ci?

ne, which probably means that in the near future I can say more about my software than "it works on my laptop" ;-) Is it possible to automatically go to the latest available tag? Best regards, Simon -- You received this message because you are subscribed to the Google Groups &qu

[sage-devel] Possible to use current Sage version in travis-ci?

x27;t pass tests in the docker image, since it uses features that are only in the latest beta. Question: Is it (reasonably) possible to use a sage beta version in travis-ci? How? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel&

[sage-devel] Re: How to use spkg-install in a travis-ci script?

ngs to a new thread. Best regards, Simon -- 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 view this discu

[sage-devel] Re: How to use spkg-install in a travis-ci script?

m/mwageringel/fgb_sage/blob/b6924832fabe86f274e4e43b7271f0f6565a72a8/.travis.yml#L20>, > > though I used pip for installing the package. That sounds very reasonable. Will definitely do so in future, when I'm done experimenting with docker and travis-ci, turning towards actual production. B

[sage-devel] Re: How to use spkg-install in a travis-ci script?

On 2019-07-30, Simon King wrote: > Perhaps I found a solution. Yes and no. Yes, it does work with the sage version on my laptop No, it does not work on travis-ci with a sage docker image. Namely, sage-dist-helpers cannot be found in $SAGE_ROOT/build/bin in the docker image: ls $SAGE_R

[sage-devel] Re: How to use spkg-install in a travis-ci script?

Perhaps I found a solution. Apparently the sdh_* shell functions are defined in $SAGE_ROOT/build/bin/sage-dist-helpers. Sourcing, so it seems, makes the spkg-install script work. Best regards, Simon On 2019-07-30, Simon King wrote: > Hi Dima, > > On 2019-07-30, Dima Pasechnik wrote

[sage-devel] Re: How to use spkg-install in a travis-ci script?

/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin If I understand correctly, the sdh_* thingies aren't executables (but I don't know what they are instead -- macros for the shell language?). I guess that's why the path is not enough. Best regards, Si

[sage-devel] How to use spkg-install in a travis-ci script?

le to spkg-install? Best regards, Simon -- 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 view this

[sage-devel] Re: Making Integer and Rational compatible with Python Fraction

o external code would be minimised by preserving backwards compatibility for Rationals. And after some deprecation period we would achieve a consistent behaviour for all kindes of fraction field elements compliant with python numbers. Best regards, Simon -- You received this message because you

[sage-devel] Re: signature missing in introspection some of the time

directly available from the class, no need to embed the information. The stuff in sage.misc.sageinspect relies on it (and strips the embedded information, if I recall correctly, when doing "stuff?"). Best regards, Simon -- You received this message because you are subscribed to the Google G

[sage-devel] Re: Matrix Inverse for Arbitrary Rings

a ring or integral domain or field is via categories ("R in Fields()"). Best regards, Simon -- 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-

[sage-devel] Re: No access to trac via git-trac ?

n do "git trac checkout", and it works. Cheers, Simon -- 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

[sage-devel] Re: How do you close a trac ticket?

rectly, the release manager will look at the tickets with positive review and take action on them (either merging them or closing them or pointing out problems that the reviewer didn't notice, etc.) Best regards, Simon -- You received this message because you are subscribed to the Google Group

[sage-devel] Re: Issue with Sage's Hilbert polynomial algorithm

its numerator is made monic or not). Best regards, Simon -- 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.

[sage-devel] Re: Issue with Sage's Hilbert polynomial algorithm

some changes in my Sage > version which would fix this? It seems to be a new bug. I have created #28110 for it. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving em

[sage-devel] Re: A question on pickling cached methods

t you say that the method is called "genus". So, probably it has not function arguments, right? It could be that the cache is stored differently in that case. I think if pickling doesn't preserve the content of the cached method then it is a bug. Best regards, Simon On 2019-06-27

[sage-devel] Re: regression between 8.7 and 8.8.rc1 with operations on polygons with vertices in a quadratic field

o patch the OS because otherwise the pexpect interface became extremely slow. Best regards, Simon -- 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

[sage-devel] Re: issues (memory leak + slowness) with multivariate polynomials

se for debugging) then everything becomes a lot slower. Does libsingular use the same memory manager than Singular? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] Re: testing for equality in new ring

Hi Daniel, I'd be interested in that topic as well. I do not try to answer your question myself, because I remember (hopefully correctly) that the recommended way to do equality testing has changed because of the switch to Python3. So, hopefully someone else can chime in... Best regards,

[sage-devel] Re: direct sums, products and other categorical constructions

Hi Simon, On 2019-05-27, Simon Brandhorst wrote: > I would agree that I want unique representation with simple "ambient" > objects (usually constructed from an integer and maybe a ring). Then with > complicated objects I am not so sure anymore. Say subgroups of a group and

[sage-devel] Re: direct sums, products and other categorical constructions

Hi Simon, I would agree that I want unique representation with simple "ambient" objects (usually constructed from an integer and maybe a ring). Then with complicated objects I am not so sure anymore. Say subgroups of a group and submodules of a module. There it might cause more tr

[sage-devel] Re: direct sums, products and other categorical constructions

Hi Simon, On 2019-05-23, Simon Brandhorst wrote: > I can live with (V, projections, coprojections) > but I dislike hiding everything in lists (or lists of lists, or lists of > lists of lists..). > Being able to type VW.projections(1) would just be so much nicer. +1. But how? I

Re: [sage-devel] direct sums, products and other categorical constructions

I can live with (V, projections, coprojections) but I dislike hiding everything in lists (or lists of lists, or lists of lists of lists..). Being able to type VW.projections(1) would just be so much nicer. -- You received this message because you are subscribed to the Google Groups "sage-dev

[sage-devel] Re: direct sums, products and other categorical constructions

of the same object, each providing different coprojections. Perhaps the "Facade" framework can be used to implement it? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

[sage-devel] Re: show() method for all sage objects

nds reasonable to me, and is basically what we do with Python's magical (double underscore) methods (namely: provide a reasonable default that shouldn't be overridden). Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" gro

[sage-devel] direct sums, products and other categorical constructions

Right now I can do sage: V = ZZ^2 sage: D = V.direct_sum(V) sage: D Free module of degree 4 and rank 4 over Integer Ring Echelon basis matrix: [1 0 0 0] [0 1 0 0] [0 0 1 0] [0 0 0 1] But the result has forgotten that it is a direct sum. Of a direct sum I expect, that it has a projection and a co-

[sage-devel] Re: show() method for all sage objects

o, a potential problem of that approach would be multiple inheritance. Best regards, Simon -- 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+un

[sage-devel] Re: Report on global function fields in Sage

> determinant computation is generally slow and for some cases terribly slow. That's something one could start with... Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Re: Report on global function fields in Sage

s with Magma? I cannot give a promise at this point, but generally I like to try and tweak code. Best regards, Simon -- 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 a

  1   2   3   4   5   6   7   8   9   10   >