[sage-devel] Re: Trac branch trouble?

[Simon King]

On 2018-07-08, Volker Braun  wrote:
> The commit SHA1 is immutable, but the branch can evolve over time.

There is a "commit" field on trac, as you know. So, why is there a
pressing need to replace the "branch" field by the content of the "commit"
field, when this makes it impossible to "git trac checkout"?

Best regards,
Simon

> On Sunday, July 8, 2018 at 8:41:56 PM UTC+2, Dima Pasechnik wrote:
>>
>> maybe this should be fixed - is there a pressing need to replace the 
>> corresponding metadata on the ticket?
>

-- 
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] Two-vertex graphs and is_prime()

[Jori Mäntysalo]

Graph({1:[2]}).is_prime() returns False, and the documentation says "A 
graph is prime if all its modules are trivial (i.e. empty, all of the 
graph or singletons)".


Is this an error, or are the two-element graphs by convention classified 
as prime graphs?


--
Jori Mäntysalo

Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

[François Bissey]

I am sorry to have introduced that in the upgrade to matplotlib 2.1. Hardcoding
was easier than setting the style to classic for every calls for the 
documentation.
The reports I had was that the default style from 2.1 onwards made the 
documentation
plots look ugly.

François

> On 9/07/2018, at 13:36, Kwankyu Lee  wrote:
> 
> Hi,
> 
> This ticket
> 
> https://trac.sagemath.org/ticket/25799
> 
> aims to remove matplotlib style 'classic' hardcoded into Sage. This makes 
> customization through the matplotlibrc file work, which fails presently.
> 
> After the ticket merged, the default matplotlib styles would be applied to 
> all Sage graphics, and Sage graphics may look subtly different than what you 
> have been used to. If you don't like this, then raise your voice to the 
> ticket. 
> 
> -- 
> 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.

-- 
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] Matplotlib plotting style 'classic' hardcoded to Sage

[Kwankyu Lee]

Hi,

This ticket

https://trac.sagemath.org/ticket/25799

aims to remove matplotlib style 'classic' hardcoded into Sage. This makes 
customization through the matplotlibrc file work, which fails presently.

After the ticket merged, the default matplotlib styles would be applied to 
all Sage graphics, and Sage graphics may look subtly different than what 
you have been used to. If you don't like this, then raise your voice to the 
ticket. 

-- 
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: Trac branch trouble?

[Volker Braun]

The commit SHA1 is immutable, but the branch can evolve over time.

On Sunday, July 8, 2018 at 8:41:56 PM UTC+2, Dima Pasechnik wrote:
>
> maybe this should be fixed - is there a pressing need to replace the 
> corresponding metadata on the ticket?

-- 
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: Trac branch trouble?

[Dima Pasechnik]

maybe this should be fixed - is there a pressing need to replace the 
corresponding metadata on the ticket?

-- 
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] unable to compile sage-8.2

[Dima Pasechnik]

I suggest that you upgrade to OSX 10.13.
At least this worked with a core2 duo macbook air (from 2011?) for me.

-- 
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 fails to build on Arch linux, possible recurrence of an old bug

[Dima Pasechnik]

we have this reported on
https://trac.sagemath.org/ticket/25391
and resolved by upgrading to python 3.6.6
(see https://trac.sagemath.org/ticket/25771)
which should be in the upcoming beta.

-- 
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 fails to build on Arch linux, possible recurrence of an old bug

[Timo Kaufmann]

Yes that is exactly https://bugs.python.org/issue33374 

 
and can be fixed by either switching to the develop branch (building 8.3rc0 
instead of 8.2) where python is already upgraded or putting the patch file 
from the python bug in the build/python/patches folder.

Am Sonntag, 8. Juli 2018 11:10:01 UTC+2 schrieb Amit Wolecki:
>
> Hi all!
> Installing sage (8.2) from maintained repo on Arch linux provided a low 
> functioning installation which symptoms are given here in the end. I then 
> tried to build sage from source, failing with a "generate-posix-vars 
> failed" and segfault. This issue resembles 
> https://bugs.python.org/issue33374 and https://bugs.python.org/issue21166 
> yet I could not deduce a solution to my case. 
> System:  ver 4.17.4 kernel, with gcc 8.1.1. Has python 2.7.15 installed 
> CPU: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz, 4 cores
>
> As for the packaged installation problem, two examples are:
> 1. sage --testall fails to start, returning:
>
> Setting permissions of DOT_SAGE directory so only you can read and write 
> it.
> no stored timings available
> Running doctests with ID 2018-07-08-11-31-28-50157d1f.
> Using --optional=optional,sage
> Doctesting entire Sage library.
> Traceback (most recent call last):
>   File "/usr/bin/sage-runtests", line 127, in 
> err = DC.run()
>   File "/usr/lib/python2.7/site-packages/sage/doctest/control.py", line 
> 1150, in run
> self.add_files()
>   File "/usr/lib/python2.7/site-packages/sage/doctest/control.py", line 
> 696, in add_files
> sagenb_loc = working_set.find(Requirement.parse('sagenb')).location
> AttributeError: 'NoneType' object has no attribute 'location'
>
> 2. installation of packages fail due to some environment confusion, for 
> example:
> [amit@amit-desk sage-8.2]$ sage -pip install surface_dynamics
> Collecting surface_dynamics
>   Using cached 
> https://files.pythonhosted.org/packages/52/8d/9d27f127f159ac58f31a318c36a633d992b5f2430f0624a01910e3c1f5b6/surface_dynamics-0.4.0.tar.gz
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
>   File "/tmp/pip-install-kf5xxcpj/surface-dynamics/setup.py", line 9, 
> in 
> from sage.env import SAGE_SRC, SAGE_VERSION
> ModuleNotFoundError: No module named 'sage'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/tmp/pip-install-kf5xxcpj/surface-dynamics/setup.py", line 11, 
> in 
> raise ValueError("this package currently installs only inside 
> SageMath (http://www.sagemath.org)")
> ValueError: this package currently installs only inside SageMath (
> http://www.sagemath.org)
> 
> 
> Command "python setup.py egg_info" failed with error code 1 in 
> /tmp/pip-install-kf5xxcpj/surface-dynamics/
>
> I tried to search for leads from these two, but couldn't understand the 
> underlying problem.
> Many thanks in advance,
> Amit.
>

-- 
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: unable to compile sage-8.2

[Samuel Lelievre]

Sun 2018-07-08 09:10:01 UTC, kenichi fujisaki:
>
> I have an old mac-air (macosx-10.6.8, intel core 2 Duo).
> I tried to compile sage-8.2 from the code source:
> i did the following:
>
> cd sage-8.2
> ./configure
> make
>
> then after a few hours. I got (cysignals-1.7.0) -fichier log en attache:
>
> [cysignals-1.7.0.p0] Error installing package cysignals-1.7.0.p0
>
> How can I fix it?

Note that it is highly recommended to upgrade to a
supported version of macOS; versions of macOS
older than 10.11 are no longer getting security fixes.

That said, the problem you are facing is that Cysignals
versions 1.7.0 or 1.7.1 won't build out-of-the-box under
MacOS <= 10.10.5, but there is a patch to correct that,
which might become part of Cysignals 1.7.2 when it is
released (it's not clear yet when that will happen).

In the meantime, to apply the patch on top of the version
of Cysignals you have, just follow the instructions at

https://groups.google.com/d/msg/sage-release/zSCoOwWazww/BL5gZfC5BAAJ 

You can start from your current partially built sage-8.2,
"make" will just resume where it started, except this time
the Cysignals build will work.

Samuel

-- 
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] Sage fails to build on Arch linux, possible recurrence of an old bug

[Antonio Rojas]

El domingo, 8 de julio de 2018 10:39:34 (CEST), Amit Wolecki escribió:

Replying to the repo package issues:


As for the packaged installation problem, two examples are:
1. sage --testall fails to start, returning:
  File 
"/usr/lib/python2.7/site-packages/sage/doctest/control.py", line 
696, in add_files

sagenb_loc = working_set.find(Requirement.parse('sagenb')).location
AttributeError: 'NoneType' object has no attribute 'location'


Install the sage-notebook package. Note that there are many other 
(expected) test failures due to using newer versions of libraries and some 
tests relying on specific installation paths. Most of those failures are 
caused by output format changes and should not affect normal Sage usage, if 
you find one that does please report it to bugs.archlinux.org


2. installation of packages fail due to some environment 
confusion, for example:
Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-install-kf5xxcpj/surface-dynamics/


You can't mix and match different installations methods. If you use the 
repository package, then you should also install all optional packages from 
the Arch repositories. Sage-specific installation commands such as 'sage 
-i' and 'sage -pip' will *not* work with the repo provided Sage package and 
will quite possibly break your installation.


--
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 fails to build on Arch linux, possible recurrence of an old bug

[Antonio Rojas]

Replying to the repo package issues:


El domingo, 8 de julio de 2018, 11:10:01 (UTC+2), Amit Wolecki escribió:
>
> As for the packaged installation problem, two examples are:
> 1. sage --testall fails to start, returning:
>
>   File "/usr/lib/python2.7/site-packages/sage/doctest/control.py", line 
> 696, in add_files
> sagenb_loc = working_set.find(Requirement.parse('sagenb')).location
> AttributeError: 'NoneType' object has no attribute 'location'
>
> Install the sage-notebook package. Note that there are many other (expected) 
> test failures due to using newer versions of libraries and some tests relying 
> on specific installation paths. Most of those failures are caused by output 
> format changes and should not affect normal Sage usage, if you find one that 
> does please report it to bugs.archlinux.org

 

> 2. installation of packages fail due to some environment confusion, for 
> example:
> [amit@amit-desk sage-8.2]$ sage -pip install surface_dynamics
>
 
You can't mix and match different installations methods. If you use the 
repository package, then you should also install all optional packages from 
the Arch repositories. Sage-specific installation commands such as 'sage 
-i' and 'sage -pip' will **not** work with the repo provided Sage package 
and will quite possibly break your installation. 

-- 
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: Trac branch trouble?

[Volker Braun]

The problem is of course that the branch is replaced by the merged commit 
sha1, so trac doesn't know any more which branch that was.



On Saturday, July 7, 2018 at 10:14:32 AM UTC+2, Simon King wrote:
>
> Hi! 
>
> I just tried to check out the branch from #18514 on a new 
> laptop, but "git trac checkout 18514" failed. Probable cause: 
> 7 hours agot the ticket was resolved as "fixed" and the branch 
> was changed from u/jdemeyer/upgrade_of_group_cohomology_spkg 
> to 65769150a96fcd8a5fcfad88a4c2173dedb11b42 
>
> I take it that the ticket's branch will be merged in the 
> soon-to-be-published develop branch. Is it a general problem 
> that trac branches can not be checked out in the time between 
> "resolved as fixed" and the release of a new beta? If yes: 
> How to work around? If no: What went wrong here? 
>
> 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.

[sage-devel] Re: unable to compile sage-8.2

[Volker Braun]

This is the MAP_ANONYMOUS issue that makes cysignals fail on EOL'ed macs. 
Might be fixed in the latest Sage beta version, I'd suggest to try that. 

But in general we can't really promise to support macs that don't get 
updates from Apple any more...



On Sunday, July 8, 2018 at 11:10:01 AM UTC+2, kenichi fujisaki wrote:
>
> I have an old mac-air (macosx-10.6.8, intel core 2 Duo). I tried to 
> compile sage-8.2 from the code source:
> i did the following:
>
> cd sage-8.2
> ./configure
> make
>
> then after a few hours. I got (cysignals-1.7.0) -fichier log en attache:
>
> [cysignals-1.7.0.p0] Error: installing with pip2 failed
> [cysignals-1.7.0.p0] 
> 
> [cysignals-1.7.0.p0] Error installing cysignals-1.7.0.p0
> [cysignals-1.7.0.p0] 
> 
> [cysignals-1.7.0.p0] 
> [cysignals-1.7.0.p0] real0m13.380s
> [cysignals-1.7.0.p0] user0m8.617s
> [cysignals-1.7.0.p0] sys0m3.114s
> [cysignals-1.7.0.p0] 
> 
> [cysignals-1.7.0.p0] Error installing package cysignals-1.7.0.p0
> [cysignals-1.7.0.p0] 
> 
>
>
> How can I fix it?
> Regards,
> KF
>
>

-- 
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] unable to compile sage-8.2

[kenichi fujisaki]

I have an old mac-air (macosx-10.6.8, intel core 2 Duo). I tried to compile 
sage-8.2 from the code source:
i did the following:

cd sage-8.2
./configure
make

then after a few hours. I got (cysignals-1.7.0) -fichier log en attache:

[cysignals-1.7.0.p0] Error: installing with pip2 failed
[cysignals-1.7.0.p0] 

[cysignals-1.7.0.p0] Error installing cysignals-1.7.0.p0
[cysignals-1.7.0.p0] 

[cysignals-1.7.0.p0] 
[cysignals-1.7.0.p0] real0m13.380s
[cysignals-1.7.0.p0] user0m8.617s
[cysignals-1.7.0.p0] sys0m3.114s
[cysignals-1.7.0.p0] 

[cysignals-1.7.0.p0] Error installing package cysignals-1.7.0.p0
[cysignals-1.7.0.p0] 



How can I fix it?
Regards,
KF

-- 
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.
Found local metadata for cysignals-1.7.0.p0
Using cached file /Users/kenfuji/sage-8.2/upstream/cysignals-1.7.0.tar.gz
cysignals-1.7.0.p0

Setting up build directory for cysignals-1.7.0.p0
Finished extraction
Applying patches from ../patches...
Applying ../patches/stack_guard.patch
patching file src/cysignals/implementation.c

Host system:
Darwin MacBook-Air-de-Ken-Fuji.local 10.8.0 Darwin Kernel Version 10.8.0: Tue 
Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/Users/kenfuji/sage-8.2/local/libexec/gcc/x86_64-apple-darwin10.8.0/7.2.0/lto-wrapper
Target: x86_64-apple-darwin10.8.0
Configured with: ../src/configure --prefix=/Users/kenfuji/sage-8.2/local 
--with-local-prefix=/Users/kenfuji/sage-8.2/local 
--with-gmp=/Users/kenfuji/sage-8.2/local 
--with-mpfr=/Users/kenfuji/sage-8.2/local 
--with-mpc=/Users/kenfuji/sage-8.2/local --with-system-zlib --disable-multilib 
--disable-nls --enable-languages=c,c++,fortran --disable-libitm 
--with-build-config=bootstrap-debug --without-isl --without-cloog  
Thread model: posix
gcc version 7.2.0 (GCC) 

Configuring cysignals-1.7.0.p0
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for library containing pari_init... -lpari
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking sys/prctl.h usability... no
checking sys/prctl.h presence... no
checking for sys/prctl.h... no
checking for backtrace... yes
checking whether PARI_SIGINT_block is declared... yes
checking for emms instruction... yes
checking whether setjmp() saves the signal mask... yes
checking for GNU libc... no
configure: creating ./config.status
config.status: creating build/src/config.h
config.status: creating build/src/cysignals/cysignals_config.h
config.status: executing build/src/cysignals/__init__.pxd commands
Installing cysignals-1.7.0.p0
Installing package cysignals using pip2
Ignoring indexes: https://pypi.python.org/simple
Processing 
/Users/kenfuji/sage-8.2/local/var/tmp/sage/build/cysignals-1.7.0.p0/src
  Running setup.py 
(path:/private/var/folders/3P/3PR+zNoGGHyvSfQTefYBMk+++TI/-Tmp-/pip-jeFG9c-build/setup.py)
 egg_info for package from 
file:///Users/kenfuji/sage-8.2/local/var/tmp/sage/build/cysignals-1.7.0.p0/src
Running command python setup.py egg_info
running egg_info
creating pip-egg-info/cysignals.egg-info
writing pip-egg-info/cysignals.egg-info/PKG-INFO
writing top-level names to pip-egg-info/cysignals.egg-info/top_level.t