Re: [sage-devel] Re: Should the "Element = ..." trick require categories?
On 2017-12-11 18:35, Simon King wrote: Well, we want to mix in P.category().element_class (an abstract class) into whatever P prescribes for its elements. So, P.element_class should be a class whose mro also contains abstract element classes defined in the category. What I did not say is that the mechanism to construct the element class of P should be coded in the category framework. Maybe you are misunderstanding me. I am *not* talking about determining the element class. I talking about the mechanism, *given* the element class, to *construct* instances of that class. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Shutdown sagenotebook and jupyter server
On Monday, December 11, 2017 at 6:27:27 AM UTC-5, Dima Pasechnik wrote: > > > > On Monday, December 11, 2017 at 9:56:17 AM UTC, Sarfo wrote: >> >> I noticed the sage notebook and jupyter servers still run in the >> background after i have exited and closed all notebooks and the browser. >> > > Do you mean a jupyter notebook whn you say "sage notebook"? > > In either case, it's true that the server might continue depending on how you exit, whether sagenb or jupiter. In the Mac app there is a specific button for this in the menu item, but elsewhere you do indeed need to return to the command line (e.g. Ctrl-D) to quit the sagenb server, at least. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Sage 8.1 building Mac-app fails
On Sunday, December 10, 2017 at 4:54:03 PM UTC-5, Michael Frey wrote: > > It appears that diskimage still has the > tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg > file open. You can find this with "sudo lsof |fgrep tmp-sage-8.1". > Killing disk image allows the "hdiutil convert -format UDBZ -o > sage-8.1-OSX_10.13.2_x86_64.app.dmg > tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg" command to succeed. > > Mike > Thanks for that debugging. That is weird that it doesn't show up elsewhere (for instance, I built 8.1.rc2, granted with an older Xcode probably, $ xcodebuild -version Xcode 7.3.1 Build version 7D1014) so hopefully we don't need to change the build script/binary-pkg script. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Should the "Element = ..." trick require categories?
Hi Jeroen, On 2017-12-11, Jeroen Demeyer wrote: > On 2017-12-11 13:31, Simon King wrote: >> Except if the basic functionality refers to category stuff. Element >> creation does! > > Can you elaborate on this? In the case where a Parent has an > element_class attribute, why should element creation involve categories? Well, we want to mix in P.category().element_class (an abstract class) into whatever P prescribes for its elements. So, P.element_class should be a class whose mro also contains abstract element classes defined in the category. What I did not say is that the mechanism to construct the element class of P should be coded in the category framework. 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Should the "Element = ..." trick require categories?
On 2017-12-11 13:31, Simon King wrote: Except if the basic functionality refers to category stuff. Element creation does! Can you elaborate on this? In the case where a Parent has an element_class attribute, why should element creation involve categories? I agree that it should still be *possible* to implement element construction in the category, but it should not be *required*. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: SageNB and ldap packages
On Monday, December 11, 2017 at 11:56:28 AM UTC, Jori Mäntysalo wrote: > > On Mon, 11 Dec 2017, Jori Mantysalo wrote: > > > But there is something wrong with those settings. I must test against a > known > > good server. > > ...and now it works on a test machine. I must still test that on real > server, where I had to say pip uninstall, pip install and sage -b to get > ldap settings to show. why would you bother with easy_install at all? All these packages you need are installable with pip. I am now trying to summarise what you did here: https://github.com/sagemath/sagenb/issues/177 Please have a look and check. Dima > > > -- > Jori Mäntysalo > -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Should the "Element = ..." trick require categories?
Hi Jeroen, On 2017-12-11, Jeroen Demeyer wrote: > On 2017-12-10 22:29, Nicolas M. Thiery wrote: >> As far as I remember, it's stipulated that any Parent should be in >> Sets. > > I don't think that this is stipulated somewhere. I think I stated it in the thematic tutorial on "how to implement new algebraic structures". > I also feel that this shouldn't be a hard requirement. I think it should! For category objects that are not sets, one should use CategoryObject. For user-visible objects in Sage that haven't anything to do with categories, one should use SageObject. And for everything else, Python gave us . > I think that the low-level basic stuff > (I consider creating elements amongst that) should work without > categories and that categories should only be used for additional > functionality on top of that. Except if the basic functionality refers to category stuff. Element creation does! >> Is there a use case where having this in Parent would be preferable? > > I can think of two reasons: the first is efficiency. +1, although currently I don't know an example where this actually results in a noticeable problem. A couple of years ago though, it was a serious bottleneck. > Second (as Travis also > said), creating elements is partially implemented in Parent and > partially in Sets. This is quite confusing and it would be best to do > this in one place. +100. I think the current implementation has too many levels of indirection and too many hooks for the implementation of a single functionality. 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. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Should the "Element = ..." trick require categories?
On 2017-12-10 22:29, Nicolas M. Thiery wrote: As far as I remember, it's stipulated that any Parent should be in Sets. I don't think that this is stipulated somewhere. I also feel that this shouldn't be a hard requirement. I think that the low-level basic stuff (I consider creating elements amongst that) should work without categories and that categories should only be used for additional functionality on top of that. Is there a use case where having this in Parent would be preferable? I can think of two reasons: the first is efficiency. Implementing stuff in Parent is faster than doing it in categories. Second (as Travis also said), creating elements is partially implemented in Parent and partially in Sets. This is quite confusing and it would be best to do this in one place. Jeroen. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: SageNB and ldap packages
On Mon, 11 Dec 2017, Jori Mantysalo wrote: But there is something wrong with those settings. I must test against a known good server. ...and now it works on a test machine. I must still test that on real server, where I had to say pip uninstall, pip install and sage -b to get ldap settings to show. -- Jori Mäntysalo
[sage-devel] Re: Shutdown sagenotebook and jupyter server
On Monday, December 11, 2017 at 9:56:17 AM UTC, Sarfo wrote: > > I noticed the sage notebook and jupyter servers still run in the > background after i have exited and closed all notebooks and the browser. > Do you mean a jupyter notebook whn you say "sage notebook"? > Please may I know how to shut them down without having to manually kill > those processes in the terminal. (I launch the notebook interface with an > executable script). Wouldn't it be great if a server shutdown button is > added to the interface? Thank you. > -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: SageNB and ldap packages
On Sun, 10 Dec 2017, Dima Pasechnik wrote: On my installation, thes files don't exist: $ ls local/lib/python2.7/site-packages/ldap/ __init__.py __init__.pyc mock.py mock.pyc server.py server.pyc Confusingly, pip also has a package called python-ldap; if I do ./sage --pip install python-ldap then I get that ldap/filter.py files indeed. But do we need it? If I just make Sage and then as admin go to Notebook Settings there is no ldap settings at all -- of course not. "./sage -i openssl" did not add that, so next I run "./sage -pip install pyopenssl" with no help. Now, both "./sage -sh"+"easy_install python-ldap" and "./sage --pip install python-ldap" gives an error about missing lber.h. So, I ran "apt-get install libldap2-dev" as root. After that there was sasl/sasl.h missing, so I ran "apt-get install libsasl2-dev". Now I was able to run "./sage -sh"+"easy_install python-ldap". But still no settings for ldap. So, next "./sage --pip install python-ldap". And here we are! Now there is ldap settings available. Now, I tested with settings Enable LDAP Authentication: On LDAP URI: ldap://ldap.forumsys.com:389/ Bind DN: cn=read-only-admin,dc=example,dc=com Bind Password: password Use GSSAPI instead of Bind DN/Password: Off Base DN: ou=mathematicians,dc=example,dc=com Username Attribute (i.e. cn, uid or userPrincipalName): uid Query timeout (seconds): 5 But there is something wrong with those settings. I must test against a known good server. -- Jori Mäntysalo
[sage-devel] Shutdown sagenotebook and jupyter server
I noticed the sage notebook and jupyter servers still run in the background after i have exited and closed all notebooks and the browser. Please may I know how to shut them down without having to manually kill those processes in the terminal. (I launch the notebook interface with an executable script). Wouldn't it be great if a server shutdown button is added to the interface? Thank you. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
