Re: [sage-devel] Should the "Element = ..." trick require categories?

[Travis Scrimshaw]

There are two things going on that I had thought were coupled together, but 
are actually not:

1 - The construction of the dynamic class element_class, which is currently 
done by Parent.__make_element_class__, which in turn indirectly calls 
Category._make_named_class via @lazy_attribute Category.element_class via 
@lazy_attribute _abstract_element_class.
2 - The initialization of a default _element_constructor_ method, which is 
done mostly in the category but there is some logic in Parent to set this 
(that should fundamentally be removed).

So everything I said above is primarily focused on 2, whereas the main 
issue is 1 and is separate from 2.

>
> Is there a use case where having this in Parent would be preferable? 
>
> My impression of the general idea is to consolidate and simplify the logic 
to make maintenance easier. I do not think we would get much of a speed 
benefit because constructing the element class should only be done once. 
Although I do not see a reason why a subcategory would want to override 
_make_named_class or have a specific element_class (to me, this breaks the 
abstraction that categories are support to have).

Part of me would like to see this logic in Element, where it dynamically 
changes/sets its class upon creation. That way, we could simply create an 
elissueement class of any type and still retain the category information, 
so we could easily have homsets with multiple element classes. 
Unfortunately I think this would significantly slow down element creation 
as all of this class and category information would have to be processed on 
every creation.

Since the element_class is really something that is used by the parent, IMO 
it is better to be in Parent than in the category. I also think if we can 
streamline some of this code, it will be easier to construct multiple 
element classes for a given parent.

Best,
Travis

-- 
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

[Michael Frey]

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

-- 
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?

[Nicolas M. Thiery]

Hi Jeroen,

On Sat, Dec 09, 2017 at 09:44:54AM +0100, Jeroen Demeyer wrote:
> The "modern" way to define a Parent class is as follows:
> 
> class MyParent(Parent):
> Element = MyElement
> def __init__(self):
> Parent.__init__(self, category=MyCategory())
> 
> One thing which surprises me is that the code to have the "Element =
> MyElement" trick work is implemented in the category of Sets. It seems to me
> that this should really be part of the general Parent infrastructure,
> independent of categories.
> 
> So, is there any particular reason why this is implemented in Sets? Are
> there any objections to changing that?

As far as I remember, it's stipulated that any Parent should be in
Sets. So, like for many other features, it's possible in principle to
implement them equivalently in Parent or Sets.ParentMethods. The
latter tends to be more flexible (e.g. a subcategory can override it).

Is there a use case where having this in Parent would be preferable?

Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" 
http://Nicolas.Thiery.name/

-- 
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

[Michael Frey]

I double checked and the Xcode IDE and Xcode Command Line Tools version is 
9.2 ( 9C40b).

When I started the Xcode IED it wanted to install some files, after that 
the script to build the man app runs further, see below.  I think it fails 
in trying to move the dmg.

I will look at the Makefile to see if I can find the problem.

Mike

sent 5283312336 bytes  received 2867200 bytes  26104590.30 bytes/sec

total size is 5273738227  speedup is 1.00

test -d 
sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/Contents/Resources/sage && 
touch sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/Contents/Resources/sage

rm -f sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/sage

ln -s Contents/Resources/sage/sage 
sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/sage

cp /Users/michael/sage-8.1/src/bin/sage-README-osx.txt 
sage-8.1-OSX_10.13.2_x86_64/README.txt

mkdir -p sage-8.1-OSX_10.13.2_x86_64/.background

cp sage-dmg-background.png sage-8.1-OSX_10.13.2_x86_64/.background/sage.png

rm -f sage-8.1-OSX_10.13.2_x86_64/Applications

ln -s /Applications/ sage-8.1-OSX_10.13.2_x86_64/Applications

hdiutil create -srcfolder sage-8.1-OSX_10.13.2_x86_64 -volname 
sage-8.1-OSX_10.13.2_x86_64 -format UDRW 
tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg



created: 
/Users/michael/sage-8.1/src/mac-app/tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg

mkdir -p mnt

hdiutil attach tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg -mountpoint mnt

/dev/disk6  GUID_partition_scheme   

/dev/disk6s1EFI 

/dev/disk6s2Apple_APFS  

/dev/disk7  EF57347C--11AA-AA11-0030654 

/dev/disk7s141504653--11AA-AA11-0030654 
/Users/michael/sage-8.1/src/mac-app/mnt

osascript arrangeIcons.applescript mnt SageMath-8.1.app

arrangeIcons.applescript:107:111: execution error: Finder got an error: 
Can’t get disk "mnt". (-1728)

make: *** [tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg] Error 1

-- 
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

[Jori Mäntysalo]

On Sun, 10 Dec 2017, Dima Pasechnik wrote:


How do I reproduce your error?


You need a working LDAP server for that. Maybe this works: 
https://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/


I'll continue with this tomorrow.

--
Jori Mäntysalo

[sage-devel] Re: Certificate of completion for Groebner Basis

[David Brandfonbrener]

Thanks! My bad for missing that in the documentation. 

On Friday, December 8, 2017 at 5:55:55 PM UTC-5, Dima Pasechnik wrote:
>
>
>
> On Friday, December 8, 2017 at 10:20:31 PM UTC, David Brandfonbrener wrote:
>>
>> When the Groebner basis is 1, is there a way to find the coefficients for 
>> a linear combination of my original generators of the ideal that is equal 
>> to 1? 
>>
>> I want to be able to provably see which polynomials in my set of 
>> generators combine to 1. 
>>
>
> This is called computing a Nullstellensatz certificate. 
> In Sage this is done using lift(), see 
> http://doc.sagemath.org/html/en/reference/polynomial_rings/sage/rings/polynomial/multi_polynomial_element.html#sage.rings.polynomial.multi_polynomial_element.MPolynomial_polydict.lift
>
>
>

-- 
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

[Dima Pasechnik]

On Sunday, December 10, 2017 at 6:04:26 PM UTC, Michael Frey wrote:
>
> I am trying to build the sage 8.1 mac-app on macOS 10.13.2 with Xcode V9.2 
> and Command Line Tools for Xcode V9.1.  
>

This combination of tools looks really strange. Do you mean that there is 
no Command Line tools for 9.2 available?

I can also point out that 9.2 came out too late to be tested for the 
release.

 

> I have been able to compile sage and run make ptests (all tests passed).
>
> When I try to build the Mac-app in sage-8.1/src/mac-app it crashes with a 
> failure to build MainMenu.nib, see below.
>

We have about one person who knows details about Mac-app, Ivan Andrus, and 
he is very busy.
 

>
> Hopefully there is an easy fix.
>
> Mike
>
> *CpResource* sage-document-cython.icns 
> build/Debug/Sage.app/Contents/Resources/sage-document-cython.icns
>
> cd /Users/michael/sage-8.1/src/mac-app
>
> builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude 
> .git -exclude .hg -resolve-src-symlinks 
> /Users/michael/sage-8.1/src/mac-app/sage-document-cython.icns 
> /Users/michael/sage-8.1/src/mac-app/build/Debug/Sage.app/Contents/Resources
>
>
> *StripNIB* English.lproj/MainMenu.nib
>
> cd /Users/michael/sage-8.1/src/mac-app
>
> export 
> XCODE_DEVELOPER_USR_PATH=/Applications/Xcode.app/Contents/Developer/usr/bin/..
>
> /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool --write 
> /Users/michael/sage-8.1/src/mac-app/build/Debug/Sage.app/Contents/Resources/English.lproj/MainMenu.nib
>  
> --output-format human-readable-text 
> /Users/michael/sage-8.1/src/mac-app/English.lproj/MainMenu.nib
>
> 2017-12-10 12:49:59.678 ibtoold[97811:5456402] [MT] DVTPlugInLoading: 
> Failed to load code for plug-in 
> com.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration 
> (/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework),
>  
> error = Error Domain=NSCocoaErrorDomain Code=3587 
> "dlopen_preflight(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration):
>  
> Library not loaded: 
> /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator
>
>   Referenced from: 
> /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit
>
>   Reason: image not found" UserInfo={NSLocalizedFailureReason=The bundle 
> is damaged or missing necessary resources., 
> NSLocalizedRecoverySuggestion=Try reinstalling the bundle., 
> NSFilePath=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
>  
> NSDebugDescription=dlopen_preflight(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration):
>  
> Library not loaded: 
> /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator
>
>   Referenced from: 
> /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit
>
>   Reason: image not found, 
> NSBundlePath=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework,
>  
> NSLocalizedDescription=The bundle 
> “IDEInterfaceBuilderCocoaTouchIntegration” couldn’t be loaded because it is 
> damaged or missing necessary resources.}, dyldError = 
> dlopen(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
>  
> 0): Library not loaded: 
> /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator
>
>   Referenced from: 
> /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit
>
>   Reason: image not found
>
> 2017-12-10 12:49:59.678 ibtoold[97811:5456402] [MT] 
> DVTPlugInExtensionFaulting: Failed to fire fault for extension 
> Xcode.InterfaceBuilderKit.PepperIntegration.Singletons: Error 
> Domain=DVTPlugInErrorDomain Code=2 "Loading a plug-in failed." 
> UserInfo={DVTPlugInIdentifierErrorKey=com.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration,
>  
> DVTPlugInExecutablePathErrorKey=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
>  
> NSLocalizedRecoverySuggestion=The plug-in or one of its prerequisite 
> plug-ins may be missing or damaged and may need to be reinstalled., 
> DVTPlugInDYLDErrorMessageErrorKey=dlopen(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
>  
> 0): Library not loaded: 
> /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator
>
>   Referenced from: 
> 

[sage-devel] Sage 8.1 building Mac-app fails

[Michael Frey]

I am trying to build the sage 8.1 mac-app on macOS 10.13.2 with Xcode V9.2 
and Command Line Tools for Xcode V9.1.  I have been able to compile sage 
and run make ptests (all tests passed).

When I try to build the Mac-app in sage-8.1/src/mac-app it crashes with a 
failure to build MainMenu.nib, see below.

Hopefully there is an easy fix.

Mike

*CpResource* sage-document-cython.icns 
build/Debug/Sage.app/Contents/Resources/sage-document-cython.icns

cd /Users/michael/sage-8.1/src/mac-app

builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude 
.git -exclude .hg -resolve-src-symlinks 
/Users/michael/sage-8.1/src/mac-app/sage-document-cython.icns 
/Users/michael/sage-8.1/src/mac-app/build/Debug/Sage.app/Contents/Resources


*StripNIB* English.lproj/MainMenu.nib

cd /Users/michael/sage-8.1/src/mac-app

export 
XCODE_DEVELOPER_USR_PATH=/Applications/Xcode.app/Contents/Developer/usr/bin/..

/Applications/Xcode.app/Contents/Developer/usr/bin/ibtool --write 
/Users/michael/sage-8.1/src/mac-app/build/Debug/Sage.app/Contents/Resources/English.lproj/MainMenu.nib
 
--output-format human-readable-text 
/Users/michael/sage-8.1/src/mac-app/English.lproj/MainMenu.nib

2017-12-10 12:49:59.678 ibtoold[97811:5456402] [MT] DVTPlugInLoading: 
Failed to load code for plug-in 
com.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration 
(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework),
 
error = Error Domain=NSCocoaErrorDomain Code=3587 
"dlopen_preflight(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration):
 
Library not loaded: 
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator

  Referenced from: 
/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit

  Reason: image not found" UserInfo={NSLocalizedFailureReason=The bundle is 
damaged or missing necessary resources., NSLocalizedRecoverySuggestion=Try 
reinstalling the bundle., 
NSFilePath=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
 
NSDebugDescription=dlopen_preflight(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration):
 
Library not loaded: 
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator

  Referenced from: 
/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit

  Reason: image not found, 
NSBundlePath=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework,
 
NSLocalizedDescription=The bundle 
“IDEInterfaceBuilderCocoaTouchIntegration” couldn’t be loaded because it is 
damaged or missing necessary resources.}, dyldError = 
dlopen(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
 
0): Library not loaded: 
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator

  Referenced from: 
/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit

  Reason: image not found

2017-12-10 12:49:59.678 ibtoold[97811:5456402] [MT] 
DVTPlugInExtensionFaulting: Failed to fire fault for extension 
Xcode.InterfaceBuilderKit.PepperIntegration.Singletons: Error 
Domain=DVTPlugInErrorDomain Code=2 "Loading a plug-in failed." 
UserInfo={DVTPlugInIdentifierErrorKey=com.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration,
 
DVTPlugInExecutablePathErrorKey=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
 
NSLocalizedRecoverySuggestion=The plug-in or one of its prerequisite 
plug-ins may be missing or damaged and may need to be reinstalled., 
DVTPlugInDYLDErrorMessageErrorKey=dlopen(/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
 
0): Library not loaded: 
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator

  Referenced from: 
/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit

  Reason: image not found, NSLocalizedDescription=Loading a plug-in 
failed., 
NSFilePath=/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework,
 
NSLocalizedFailureReason=The plug-in 
“com.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration” at path 
“/Applications/Xcode.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework”
 
could not be loaded.  The plug-in or one of its prerequisite plug-ins may 
be missing or damaged., NSUnderlyingError=0x7fd2c160a8d0 {Error 

Re: [sage-devel] Re: Should the "Element = ..." trick require categories?

[Jeroen Demeyer]

On 2017-12-10 15:39, Travis Scrimshaw wrote:

My guess is so that one could define an _element_constructor_ at the
category level.


I see. The problem is that the category comes after Parent in the MRO, 
right? So if Parent implements _element_constructor_, then the category 
cannot.


--
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-combinat-devel] sage-devel: """Should the "Element = ..." trick require categories?"""

[Samuel Lelievre]

This is just to mention to sage-combinat-devel readers
a sage-devel discussion on the topic

Should the "Element = ..." trick require categories?
https://groups.google.com/d/topic/sage-devel/Q9nuzwM7YRA/discussion

Cheers,
Samuel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Installing Sage 8.0 (gcc-7.2.0 won't install)

[Michael Frey]

I upgraded to Command Line Tools for Xcode V9.1 and Sage 8.1 now compiles.

-- 
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?

[Travis Scrimshaw]

My guess is so that one could define an _element_constructor_ at the 
category level. Although IMO, the possibility of that being meaningful is 
low considering you have to know something about the implementation of the 
associated element class in order to do this, which breaks the 
abstract-ness of the category code. There is one very natural exception to 
this: façade parents, which is a category-level implementation/property. So 
you will have to address this, but my current impression from reading the 
code is the current indirection is not necessary.

Best,
Travis

On Saturday, December 9, 2017 at 2:45:01 AM UTC-6, Jeroen Demeyer wrote:
>
> The "modern" way to define a Parent class is as follows: 
>
> class MyParent(Parent): 
>  Element = MyElement 
>  def __init__(self): 
>  Parent.__init__(self, category=MyCategory()) 
>
> One thing which surprises me is that the code to have the "Element = 
> MyElement" trick work is implemented in the category of Sets. It seems 
> to me that this should really be part of the general Parent 
> infrastructure, independent of categories. 
>
> So, is there any particular reason why this is implemented in Sets? Are 
> there any objections to changing that? 
>
>
> 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

[Nils Bruin]

On Saturday, December 9, 2017 at 1:15:12 AM UTC-5, Jori Mäntysalo wrote:
>
>
> It is for publishing notebooks to the world, not for sharing a notebook 
> within a group (or to a teacher). 
>
> That's a problem that is solved in the jupyter world as well:

https://nbviewer.jupyter.org/

If you want more control over who it is shared with (or where the actual 
notebook is stored) perhaps installing your own nbviewer somewhere is 
doable. 

-- 
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

[Dima Pasechnik]

On Sunday, December 10, 2017 at 11:17:35 AM UTC, 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?
>
>
How do I reproduce your error?
Perhaps it could be some problem related to absolute imports, something we 
switched to in the recent sagenb.

 

>
>
> On Sunday, December 10, 2017 at 9:25:21 AM UTC, Jori Mäntysalo wrote:
>>
>> On Sun, 10 Dec 2017, Dima Pasechnik wrote: 
>>
>> > Could you locate the python file this command is in? 
>>
>> $ fgrep 'import strf_secs' -R . 
>> ./local/lib/python2.7/site-packages/ldap/filter.py:from ldap.functions 
>> import strf_secs 
>> ./local/lib/python3.6/site-packages/python_ldap-3.0.0b1-py3.6-linux-x86_64.egg/ldap/filter.py:from
>>  
>> ldap.functions import strf_secs 
>> ./local/lib64/python2.7/site-packages/ldap/filter.py:from ldap.functions 
>> import strf_secs 
>> ./local/lib64/python3.6/site-packages/python_ldap-3.0.0b1-py3.6-linux-x86_64.egg/ldap/filter.py:from
>>  
>> ldap.functions import strf_secs 
>>
>> -- 
>> 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.

Re: [sage-devel] Re: SageNB and ldap packages

[Dima Pasechnik]

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?



On Sunday, December 10, 2017 at 9:25:21 AM UTC, Jori Mäntysalo wrote:
>
> On Sun, 10 Dec 2017, Dima Pasechnik wrote: 
>
> > Could you locate the python file this command is in? 
>
> $ fgrep 'import strf_secs' -R . 
> ./local/lib/python2.7/site-packages/ldap/filter.py:from ldap.functions 
> import strf_secs 
> ./local/lib/python3.6/site-packages/python_ldap-3.0.0b1-py3.6-linux-x86_64.egg/ldap/filter.py:from
>  
> ldap.functions import strf_secs 
> ./local/lib64/python2.7/site-packages/ldap/filter.py:from ldap.functions 
> import strf_secs 
> ./local/lib64/python3.6/site-packages/python_ldap-3.0.0b1-py3.6-linux-x86_64.egg/ldap/filter.py:from
>  
> ldap.functions import strf_secs 
>
> -- 
> 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.

Re: [sage-devel] Re: SageNB and ldap packages

[Jori Mäntysalo]

On Sun, 10 Dec 2017, Dima Pasechnik wrote:


Could you locate the python file this command is in?


$ fgrep 'import strf_secs' -R .
./local/lib/python2.7/site-packages/ldap/filter.py:from ldap.functions import 
strf_secs
./local/lib/python3.6/site-packages/python_ldap-3.0.0b1-py3.6-linux-x86_64.egg/ldap/filter.py:from
 ldap.functions import strf_secs
./local/lib64/python2.7/site-packages/ldap/filter.py:from ldap.functions import 
strf_secs
./local/lib64/python3.6/site-packages/python_ldap-3.0.0b1-py3.6-linux-x86_64.egg/ldap/filter.py:from
 ldap.functions import strf_secs

--
Jori Mäntysalo

Re: [sage-devel] Re: SageNB and ldap packages

[Dima Pasechnik]

Could you locate the python file this command is in? 

-- 
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.