> @Travis:
>
> > I'd also perhaps not use a classcall on the morphism, but instead
> explicitly construct the Homset (parent) and from that, construct the
> corresponding element to simplify the class (and it's a natural interface).
>
> I must admit that I do not understand, but I hope I will o
If that's how you want to do them, then perhaps what you should do is have
a class which holds the actual map data from FindStat and handles all of
the webpage interaction, and then have a a Parent/Element pair in which the
Element class holds a list of these FindStatMap class instances. You'll
Hi Eric and Travis!
I'm afraid I need more help. I looked at the FreeModuleHomset example, but
I couldn't quite match it with my situation.
The database contains a bunch of "combinatorial collections", like Dyck
words or graphs. I think these should be the objects of my category, so I
guess
On Fri, Jun 5, 2015 at 7:58 PM, kcrisman wrote:
> Harald, any ideas on what remains to replace this?
No idea, but I've made this issue to add a simple redirection page.
https://github.com/sagemath/website/issues/52
-- harald
--
You received this message because you are subscribed to the Googl
Great, thank you!
How can I find out which methods I have to implement when inheriting from
Morphism? One possibly important thing: my maps can not be called...
Best,
Martin
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
Hi Travis,
Le dimanche 7 juin 2015 17:17:36 UTC+2, Travis Scrimshaw a écrit :
>
> Hey Martin,
>It looks like you want to look at a Homset class, in particular, a good
> model might be tensor/modules/free_module_homset.py.
>
I wrote my answer before getting yours...The FreeModuleHomset exam
Hi,
If FindStatMap's are morphisms, why don't you make the class FindStatMaps
inherit from Homset (instead of directly from Parent) and the class
FindStatMap inherit from Morphism (instead of directly from Element) ? I.e.
why don't you use something like:
class FindStatMap(Morphism):
def
Hey Martin,
It looks like you want to look at a Homset class, in particular, a good
model might be tensor/modules/free_module_homset.py. I'd also perhaps not
use a classcall on the morphism, but instead explicitly construct the
Homset (parent) and from that, construct the corresponding elemen
On 2015-06-07 11:39, Volker Braun wrote:
Deleting the old packages will also break optional packages on all old
Sage versions
These are already broken by the moving of the files on the website: the
sage-5.x scripts look in
http://www.sagemath.org/spkg/optional/list
which no longer exists.
--
Y
Hi there!
I tried to improve on my FindStat interface
(trac.sagemath.org/ticket/17818), by making the instances of the class
FindStatMap elements of a new class FindStatMaps.
I used the pattern below (reduced to an absolute minimum. I must admit,
this is a lot of code for saying that a FindSt
On 2015-06-07 11:39, Volker Braun wrote:
Deleting the old packages will also break optional packages on all old
Sage versions
Like Nathann suggested, moving packages to archive will not break old
versions.
there should be a sensible deprecation period before doing so.
We cannot retroactively
On Sunday, June 7, 2015, Jeroen Demeyer wrote:
> On 2015-06-07 11:27, William Stein wrote:
>
>> Why do you claim that genus2reduction is "simply no longer used in Sage"?
>>
> http://trac.sagemath.org/ticket/15808
>
>
Ahh. That's an extremely good reason. Very nice!
> --
> You received this mes
On 2015-06-07 11:27, William Stein wrote:
Why do you claim that genus2reduction is "simply no longer used in Sage"?
http://trac.sagemath.org/ticket/15808
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop rec
On Sunday, June 7, 2015 at 9:51:11 AM UTC+2, Nathann Cohen wrote:
>
> Yo !
>
> I think it adding a link to that page on the sagemath.org
>> homepage would make sense, what do you think?
>>
>
> I guess. You can make a pull request:
> https://github.com/sagemath/website
>
for the record:
https://g
> If you type "sage -f extcode" for an old Sage version then I'm pretty sure
> that the archive folder is not being searched.
In the following patch (from three years ago) the 'archive' repository
was already in use.
http://trac.sagemath.org/ticket/13373
Thus it would only be a problem for >3yo
If you type "sage -f extcode" for an old Sage version then I'm pretty sure
that the archive folder is not being searched.
On Sunday, June 7, 2015 at 11:45:30 AM UTC+2, Nathann Cohen wrote:
>
> > Deleting the old packages will also break optional packages on all old
> Sage
> > versions, so the
> Deleting the old packages will also break optional packages on all old Sage
> versions, so there should be a sensible deprecation period before doing so.
Isn't there a 'archive/' folder made precisely for that?
Moving the unused packages to 'archive/' would work, wouldn't it?
- It would not app
Deleting the old packages will also break optional packages on all old Sage
versions, so there should be a sensible deprecation period before doing so.
IMHO the whole old-style package stuff should be removed at one point,
which would greatly simplify the entire package management. We would need
+1. Such a page is very nice to have, and even nicer to link to from the
main web page. The wiki, unfortunately, as a "marketing" page is not very
pretty (not at all as pretty as the job offer page for the OpenDreamKit
positions, for instance).
I added some information on the coding theory proj
>
> My main question is: how does one change the online package lists?
>
As far as I know Harald (and perhaps Volker) are the only ones who can
changed that. That's why I sent them this email earlier.
Nathann
--
You received this message because you are subscribed to the Google Groups
"sag
On Sun, Jun 7, 2015 at 2:18 AM, Jeroen Demeyer wrote:
> Hello,
>
> What's the current status on the old-style packages on the mirrors? Has the
> move been completed?
>
> I am asking because there are still many obsolete old-style packages on
> those servers. All packages which are
> 1. superseded
Hello,
What's the current status on the old-style packages on the mirrors? Has
the move been completed?
I am asking because there are still many obsolete old-style packages on
those servers. All packages which are
1. superseded by a new-style package (like zeromq), or
2. are currently in the
Yo !
I think it adding a link to that page on the sagemath.org
> homepage would make sense, what do you think?
>
I guess. You can make a pull request:
https://github.com/sagemath/website
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
T
On 2015-06-06 11:38, Dima Pasechnik wrote:
WTF? Can you at least give a notice to fix the doctests?!
This is the notice:
FYI: `gap_packages` optional doctests don't pass, so the package was moved
to experimental.
Maybe I should explain the reason for all this: it's about
http://trac.sage
24 matches
Mail list logo
