Hello,
I'm attempting to finish two pull requests:
https://github.com/sagemath/sage/pull/38455
https://github.com/sagemath/sage/pull/39200
They do depend on one another in that 38455 requires extend=true from
39200. However, right now both PRs seem to be passing all the major "build
and test" CI
I think a new label like “r: unresponsive” makes a lot of sense as opposed
to “r: invalid”.
Best,
Jackson
On Thu, Jan 23, 2025 at 4:56 PM Kwankyu Lee wrote:
> The reviewer may close unresponsive PRs with the label "r: invalid". By
> the way, "r" stands for resolution. Or we could make up a new
I had a similar thought but didn’t know if it was possible. I don’t really
understand the idea of being religious about not touching someone’s PR if
they were the one that opened it. Surely just getting the code finished and
merged is more important, and being able to rebase rather than abandoning
That sounds reasonable to me. I have a couple open PRs, one of which
originated months ago, but I try to stay current with it. I don't see a
problem with closing it with an appropriate tag with the possibility of
reopening down the road if they do respond.
Best,
Jackson
On Tue, Jan 21, 2025 at 3:
Thanks for the tips. Some changes have been made and now (almost) all tests
are passing.
On Wed, Dec 11, 2024 at 7:37 PM Nils Bruin wrote:
> Read on for the other failures. If you look up line 1953, you'll see it's
> inside a try/except. You're triggering the KeyError, so it's the outer one
> fo
It sounds like you are going to be fighting this thing if you stick with
it. I'm seeing some pretty nice refurbished machines with 8gb memory on
eBay on the cheap. If that's not an option, I wouldn't think twice about
recycling it and waiting until you have a machine that runs Sage easily.
On Fri,
Hi all,
I am attempting to move some code from symmetric_group_algebra to
symmetric_group_representations. We are constructing a unitary DFT for S_n
over F_{q^2} and number fields, and an intermediate step was constructing
unitary rep'ns. There's an alternate way to construct the unitary DFT wh
Without knowing the details of Guava, I recently had to install and use the
GAP `forms` package. It was a little tricky to load it properly using
gap.eval, but what ended up working better was libgap,
libgap.LoadPackage(“forms”)
and you can check the Boolean return type to see if it loaded proper
[conj_square_root(d) for d in diag])
return factor_diag*A.inverse()
The GAP code performs the row operations explicitly and is lengthy. For
now, we simply avoid any call to libgap, and tests are beginning to pass.
Thanks,
Jackson
On Thu, Dec 5, 2024 at 9:14 PM Michael Orlitzky
wrote:
> On 20
ve installed `forms`.
On Thu, Dec 5, 2024 at 8:16 PM Michael Orlitzky
wrote:
> On 2024-12-05 15:23:35, Jackson Walters wrote:
> >
> > Ah, thank you. Any idea if loading packages via
> libgap.LoadPackage("forms") is
> > expected to work?
>
> Yes, but only i
s(libgap)
> from sage.libs.gap.libgap import libgap
> David
>
> On Thu, Dec 5, 2024 at 5:37 PM Jackson Walters
> wrote:
>
>> Perhaps I can just use
>>
>> from sage.libs.gap.libgap import libgap
>>
>> On Thursday, December 5, 2024 at 5:34:45 PM UTC-5 Jacks
in
sage.libs.gap.libgap.Gap.__getattr__
<https://github.com/sagemath/sage/actions/runs/12189420625/job/34004520120?pr=38455#step:16:58>
raise AttributeError(f'No such attribute: {name}.')
<https://github.com/sagemath/sage/actions/runs/12189420625/job/34004520120?pr=38455#step:16
Perhaps I can just use
from sage.libs.gap.libgap import libgap
On Thursday, December 5, 2024 at 5:34:45 PM UTC-5 Jackson Walters wrote:
> Hi all,
>
> Probably pretty obvious, but I need to call libgap for the following
> function:
>
> def unitary_change_of_basis(U,q):
>
Hi all,
Probably pretty obvious, but I need to call libgap for the following
function:
def unitary_change_of_basis(U,q):
if U.nrows() == 1 and U.ncols() == 1:
return matrix(F,[[factor_scalar(U[0,0])]])
libgap.LoadPackage("forms")
return matrix(F,libgap.BaseChangeToCanonical(lib
;> @jacksonwalters
>>
>> It appears to be resolved - I am able to comment on issues now.
>>
>> Thanks,
>> Jackson
>>
>> On Tue, Dec 3, 2024 at 3:19 PM David Roe wrote:
>>
>>> What is your github username?
>>> David
>>>
>&
@jacksonwalters
It appears to be resolved - I am able to comment on issues now.
Thanks,
Jackson
On Tue, Dec 3, 2024 at 3:19 PM David Roe wrote:
> What is your github username?
> David
>
> On Tue, Dec 3, 2024 at 2:56 PM Jackson Walters
> wrote:
>
>> It seems I am not
It seems I am not able to add comments to issues or PRs on GitHub. Is this
a GitHub issue or something specifically with Sage?
--
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
I will certainly second that, thank you Marc! I use the app on macOS and
it's been very smooth and nice to have. I'm sure I used it in grad school,
as well. I do encourage people to use it when the topic arises, and it's
cool to see the numbers double. Congrats!
On Sat, Nov 30, 2024 at 12:12 PM G.
Hi all,
I am making some changes to `symmetric_group_representations.py`, and it
would be useful to test them locally before committing them to a PR. I
haven't found it necessary to build Sage from source, but I'd like to now.
I am following the instructions in "Instructions to Build from Sourc
19 matches
Mail list logo
