Re: [sage-support] Using topcom after install (Sage 8.9, Mac Catalina)

2020-02-11 Thread 'moep' via sage-support
The issue has a simple resolution, which I overlooked: One has to set the internal machine to topcom, using PointConfiguration.set_engine('topcom'). I'm not sure why I didn't have to include it explicitly in every notebook on older versions. But it's not a big deal. On Sunday, February 9, 2020

Re: [sage-support] Using topcom after install (Sage 8.9, Mac Catalina)

2020-02-09 Thread 'moep' via sage-support
Sorry, if there is a confusion regarding the file location, but I simply replaced the actual path with "x" for privacy reason. The same kind of error message also pops up if I create a new file in the home directory. For example, if P is a point configuration, then let p1 = P.restrict_to_reg

Re: [sage-support] Using topcom after install (Sage 8.9, Mac Catalina)

2020-02-07 Thread Dima Pasechnik
It's hard to say, but the root of the filesystem, as in '/x.sage' is a very weird location to have any work files in, and it would be not unusual for the OS to be suspicious of something fishy going on. Normally one would keep everything in the home directory, i.e. in ~/. On Fri, Feb 7, 2020 a

[sage-support] Using topcom after install (Sage 8.9, Mac Catalina)

2020-02-07 Thread 'moep' via sage-support
Hi, I have a problem using the package topcom on my Mac (running Catalina). After installing it (as I confirmation, I checked: sage: is_package_installed('topcom') True ), I wanted to run some older notebooks with polytope triangulations. However, I get the error shown below. Is this related to