On Mon, Jul 11, 2022 at 9:22 PM Matthias Koeppe
wrote:
>
> You may have used "brew unlink" on these packages,
if you have X in your path, "brew X" won't link X, it will be
installed in a keg-only way.
I think that's how it went the way it went.
> but they are not keg-only packages.
> Compare:
Alright, thank you.
On Tuesday, July 12, 2022 at 2:08:42 AM UTC-4 dim...@gmail.com wrote:
>
>
> On Tue, 12 Jul 2022, 02:37 Josh Mundinger, wrote:
>
>> When I run conjugacy_classes_representatives() on a sufficiently large
>> permutation group, it seems that the ordering that representatives are
On Tue, 12 Jul 2022 at 14:14, Josh Mundinger wrote:
>
> Alright, thank you.
>
> On Tuesday, July 12, 2022 at 2:08:42 AM UTC-4 dim...@gmail.com wrote:
>>
>>
>>
>> On Tue, 12 Jul 2022, 02:37 Josh Mundinger, wrote:
>>>
>>> When I run conjugacy_classes_representatives() on a sufficiently large
>>> p
Dear sage-devel,
I am running into an issue with computing isogeny classes of elliptic
curves over number fields.
Here is what I entered:
K. = QuadraticField(4569)
myJ = 46969655/32768
E = EllipticCurve(j=K(myJ))
C = E.isogeny_class()
This raises a KeyError in the first instance, which seems t
On 12/07/2022 16:59, John Cremona wrote:
On Tue, 12 Jul 2022 at 14:14, Josh Mundinger wrote:
Alright, thank you.
On Tuesday, July 12, 2022 at 2:08:42 AM UTC-4 dim...@gmail.com wrote:
On Tue, 12 Jul 2022, 02:37 Josh Mundinger, wrote:
When I run conjugacy_classes_representatives() on a s
Barinder, I'll look into this (tomorrow) -- it's my code. Please open
a ticket and CC me. It's happening in the code to reduce a model with
respect to scaling by units.
John
On Tue, 12 Jul 2022 at 16:19, Barinder Banwait wrote:
>
> Dear sage-devel,
>
> I am running into an issue with computing
Bullet points are used in sage mainly in two places:
(1) AUTHORS section in the doc string of a file
(2) INPUTS section in the doc string of a class or function definition
In (1), we usually look from the top to the bottom. This list may get
longer and longer. So no blank line between points se
I am "no" to having a Sage policy dictating blank lines, and I am also "no"
to having a policy dictating no blank lines. As Kwankyu Lee points out,
sometimes a blank line is useful, sometimes it isn't. We should leave it up
to the judgment of each individual developer.
On Tuesday, July 12, 202
On Wednesday, July 13, 2022 at 12:13:28 PM UTC+9 John H Palmieri wrote:
> I am "no" to having a Sage policy dictating blank lines, and I am also
> "no" to having a policy dictating no blank lines.
>
We do have conventions in the developer manual by which sage developers are
"dictated". Specifi