Re: [sage-devel] Build error

[David . Coudert]

I tried some of the suggestions:
1) deleting SAGE_LOCAL/lib/libpython* and then make -> failed
2) make distclean && make build -> success

I still have to add the optional packages I need, but it's working.

Thanks.
David.

-- 
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] Development suggestion

[kcrisman]

On Wednesday, December 6, 2017 at 11:34:06 PM UTC-5, William wrote:
>
> On Wed, Dec 6, 2017 at 7:09 PM, David Cousens  > wrote: 
> > Hi 
> > 
> > Has anyone considered making the menu section of the sage Web interface 
> non 
> > scrolling and only making the worksheet cell part of the interface 
> > scrollable. 
>
>
Great idea, but a) sagenb interface, while working fine, has a fairly 
moribund development b) the CoCalc .sagews files do have this ability c) 
Jupyter apparently has this as well, at least on CoCalc.
 

> What is " the sage Web interface"? 
>
>
I assume the poster is referring to the legacy Sage notebook server.
 

> > I find myself often scrolling back through a large page to reach the 
> menu 
> > and then having to scroll back to where I was in the worksheet. 
> > 
>
>
Me too. 

-- 
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: [OT] Re: Issue with quick start

[kcrisman]

>
> In German, we have an abbreviation for "compulsive abbreviation 
> disorder": Aküfi ("Abkürzungsfimmel", which roughly means 
> "abbrevimania"). 


Nie gehört but I love it! 

-- 
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: Another build error

[Kwankyu Lee]

On Friday, December 8, 2017 at 8:30:48 AM UTC+9, Travis Scrimshaw wrote:
>
>
>
>> Anyway. The branch used to be an old one. I checked it out and then 
>> rebased on top of the latest develop. Do I understand correctly that 
>> while rebasing, git failed to remove the cypari2 folder? 
>>
>> IMO, a better practice is to merge in old branches to a branch based off 
> develop. 
>

I also adopted this practice after many trial and errors. Shouldn't we make 
it an official recommendation and include it in the developer manual? On 
the other hand, one problem with the practice is that the new branch based 
off develop does not have the tracking information of the old branch.

-- 
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: Another build error

[Travis Scrimshaw]

>
> Anyway. The branch used to be an old one. I checked it out and then 
> rebased on top of the latest develop. Do I understand correctly that 
> while rebasing, git failed to remove the cypari2 folder? 
>
> IMO, a better practice is to merge in old branches to a branch based off 
develop. If you want to rebase, then run rebase. That way you never have 
old cruft and have to watch Sage do a massive rebuild of things with only 
changed timestamps. For example

$ git checkout -b branch_name develop
$ git merge branch_name
$ git rebase develop

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.

Re: [sage-devel] Build error

[Dima Pasechnik]

yeah, I agree that a stale library is the most probable reason for this error.

-- 
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: Another build error

[Simon King]

On 2017-12-07, François Bissey  wrote:
> Seems like it. Which is why I asked if there was anything in it.

I think it was empty before I removed it.

-- 
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: Build error

[François Bissey]

> On 8/12/2017, at 11:57, Simon King  wrote:
> 
> I just see the following in the diff:
> 
> +from libc.string cimport memcpy
> +include "cysignals/signals.pxi"
> +include 'sage/ext/stdsage.pxi'
> 
> I recall from some trac ticket I was involved in that all three of the
> above statements should be replaced. But before I start searching my
> tickets: Can you perhaps remind me what I should replace the above
> statements with?

Sorry, I don’t know on the top of my mind. I would have to do the research
the same as you.

François

-- 
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: Build error

[Simon King]

On 2017-12-07, Simon King  wrote:
> On 2017-12-07, François Bissey  wrote:
>> No. I believe we stopped relying on that file when upgrading to cysignals 
>> 1.6.x.
>> So the proper include to get that file may have been removed from somewhere.
>> Your branch would be quite peculiar to be caught between two changes.
>> Could you rebase it?
>
> It already was rebased on the current develop branch.

But it seems that while merging changes, I did something wrong:
One of the changes used to be the right thing, but won't work with
cysignals 1.6.x.

I just see the following in the diff:

+from libc.string cimport memcpy
+include "cysignals/signals.pxi"
+include 'sage/ext/stdsage.pxi'

I recall from some trac ticket I was involved in that all three of the
above statements should be replaced. But before I start searching my
tickets: Can you perhaps remind me what I should replace the above
statements with?

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: Another build error

[François Bissey]

> On 8/12/2017, at 11:48, Simon King  wrote:
> 
> Hi François,
> 
> On 2017-12-07, François Bissey  wrote:
>>> Strangely, git status mentions
>>>   src/sage/libs/cypari2/
>>> which my local branch is *not* touching. So, what's happening?
>>> 
>> 
>> Anything in that folder? That folder has been removed when cypari2 has been 
>> made a separate package. git sometimes don’t remove folders that have been 
>> removed. What is the exact git status for that folder?
> 
> Sorry, I cannot tell exactly, as I deleted the folder and then tried
> "make" (without "make distclean") again. It did not succeed.
> 
> Anyway. The branch used to be an old one. I checked it out and then
> rebased on top of the latest develop. Do I understand correctly that
> while rebasing, git failed to remove the cypari2 folder?
> 

Seems like it. Which is why I asked if there was anything in it.

François

-- 
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: Another build error

[Simon King]

Hi François,

On 2017-12-07, François Bissey  wrote:
>> Strangely, git status mentions
>>src/sage/libs/cypari2/
>> which my local branch is *not* touching. So, what's happening?
>> 
>
> Anything in that folder? That folder has been removed when cypari2 has been 
> made a separate package. git sometimes don’t remove folders that have been 
> removed. What is the exact git status for that folder?

Sorry, I cannot tell exactly, as I deleted the folder and then tried
"make" (without "make distclean") again. It did not succeed.

Anyway. The branch used to be an old one. I checked it out and then
rebased on top of the latest develop. Do I understand correctly that
while rebasing, git failed to remove the cypari2 folder?

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.

[sage-devel] Re: Build error

[Simon King]

On 2017-12-07, François Bissey  wrote:
> No. I believe we stopped relying on that file when upgrading to cysignals 
> 1.6.x.
> So the proper include to get that file may have been removed from somewhere.
> Your branch would be quite peculiar to be caught between two changes.
> Could you rebase it?

It already was rebased on the current develop branch.

-- 
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: Another build error

[François Bissey]

> On 8/12/2017, at 11:12, Simon King  wrote:
> 
> On 2017-12-07, Simon King  wrote:
>> Hi!
>> 
>> Building Sage again, I get the error
>>  InternalError: Internal compiler error: 'cysignals/signals.pxi' not
>>  found
>> 
>> Unfortunately, the error did not go away after "make distclean".
>> 
>> What can I do? The error occurs on some local branch (different from
>> develop), however I didn't touch cysignals.
> 
> Strangely, git status mentions
>src/sage/libs/cypari2/
> which my local branch is *not* touching. So, what's happening?
> 

Anything in that folder? That folder has been removed when cypari2 has been 
made a separate package. git sometimes don’t remove folders that have been 
removed. What is the exact git status for that folder?

François

-- 
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: Another build error

[Simon King]

On 2017-12-07, Simon King  wrote:
> Hi!
>
> Building Sage again, I get the error
>   InternalError: Internal compiler error: 'cysignals/signals.pxi' not
>   found
>
> Unfortunately, the error did not go away after "make distclean".
>
> What can I do? The error occurs on some local branch (different from
> develop), however I didn't touch cysignals.

Strangely, git status mentions
src/sage/libs/cypari2/
which my local branch is *not* touching. So, what's happening?

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: Build error

[François Bissey]

No. I believe we stopped relying on that file when upgrading to cysignals 1.6.x.
So the proper include to get that file may have been removed from somewhere.
Your branch would be quite peculiar to be caught between two changes.
Could you rebase it?

François

> On 8/12/2017, at 10:56, Simon King  wrote:
> 
> Hi!
> 
> On 2017-12-07, François Bissey  wrote:
>> OK this looks suspiciously like 
>> https://bugs.python.org/issue30074
>> which was fixed by 
>> https://github.com/python/cpython/pull/1154
>> which should be in 2.7.14.
>> What I suspect is happening is that those failures happen when
>> people upgrade python from 2.7.13 (or older) to 2.7.14.
>> I have a feeling that when the extension (and there is more than one failing)
>> is loaded to be tested as being successfully built, the wrong libpython is 
>> loaded.
>> Because of our use of rpath, libpython from python 2.7.13 is used and 
>> missing 
>> that particular symbol.
>> If this is really the case, deleting SAGE_LOCAL/lib/libpython* should be 
>> enough
>> to fix the issue.
> 
> Sorry, I missed your replies before I posted a new thread for a
> seemingly different error.
> 
> Would the problem you mention also be responsible for the following
> failure when building sagelib?
> 
> make[3]: Entering directory '/home/king/Sage/git/sage/src'
> make[3]: warning: -jN forced in submake: disabling jobserver mode.
> cd . && export\
>SAGE_ROOT=/doesnotexist   \
>SAGE_SRC=/doesnotexist\
>SAGE_SRC_ROOT=/doesnotexist   \
>SAGE_DOC_SRC=/doesnotexist\
>SAGE_BUILD_DIR=/doesnotexist  \
>SAGE_PKGS=/home/king/Sage/git/sage/build/pkgs\
> && sage-python23 -u setup.py --no-user-cfg build install
> Discovering Python/Cython source code
> Discovered Python/Cython sources, time: 0.61 seconds.
> running build
> Generating auto-generated sources
> Building interpreters for fast_callable
> -> First build of interpreters
> running build_cython
> Enabling Cython debugging support
> Updating Cython code
> 
> Traceback (most recent call last):
>  File "setup.py", line 942, in 
>ext_modules = ext_modules)
>  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/core.py", line 
> 151, in setup
>dist.run_commands()
>  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/dist.py", line 
> 953, in run_commands
>self.run_command(cmd)
>  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/dist.py", line 
> 972, in run_command
>cmd_obj.run()
>  File "setup.py", line 847, in run
>build.run(self)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/distutils/command/build.py", 
> line 127, in run
>self.run_command(cmd_name)
>  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/cmd.py", line 
> 326, in run_command
>self.distribution.run_command(command)
>  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/dist.py", line 
> 972, in run_command
>cmd_obj.run()
>  File "setup.py", line 370, in run
>cache=False,
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 920, in cythonize
>aliases=aliases)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 815, in create_extension_list
>kwds = deps.distutils_info(file, aliases, base).values
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 670, in distutils_info
>return (self.transitive_merge(filename, self.distutils_info0, 
> DistutilsInfo.merge)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 680, in transitive_merge
>node, extract, merge, seen, {}, self.cimported_files)[0]
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 685, in transitive_merge_helper
>deps = extract(node)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 650, in distutils_info0
>cimports, externs, incdirs = self.cimports_externs_incdirs(filename)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Utils.py", 
> line 44, in wrapper
>res = cache[args] = f(self, *args)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
>  line 555, in cimports_externs_incdirs
>for include in self.included_files(filename):
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Utils.py", 
> line 44, in wrapper
>res = cache[args] = f(self, *args)
>  File 
> "/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",

[sage-devel] Re: Build error

[Simon King]

Hi!

On 2017-12-07, François Bissey  wrote:
> OK this looks suspiciously like 
> https://bugs.python.org/issue30074
> which was fixed by 
> https://github.com/python/cpython/pull/1154
> which should be in 2.7.14.
> What I suspect is happening is that those failures happen when
> people upgrade python from 2.7.13 (or older) to 2.7.14.
> I have a feeling that when the extension (and there is more than one failing)
> is loaded to be tested as being successfully built, the wrong libpython is 
> loaded.
> Because of our use of rpath, libpython from python 2.7.13 is used and missing 
> that particular symbol.
> If this is really the case, deleting SAGE_LOCAL/lib/libpython* should be 
> enough
> to fix the issue.

Sorry, I missed your replies before I posted a new thread for a
seemingly different error.

Would the problem you mention also be responsible for the following
failure when building sagelib?

make[3]: Entering directory '/home/king/Sage/git/sage/src'
make[3]: warning: -jN forced in submake: disabling jobserver mode.
cd . && export\
SAGE_ROOT=/doesnotexist   \
SAGE_SRC=/doesnotexist\
SAGE_SRC_ROOT=/doesnotexist   \
SAGE_DOC_SRC=/doesnotexist\
SAGE_BUILD_DIR=/doesnotexist  \
SAGE_PKGS=/home/king/Sage/git/sage/build/pkgs\
&& sage-python23 -u setup.py --no-user-cfg build install
Discovering Python/Cython source code
Discovered Python/Cython sources, time: 0.61 seconds.
running build
Generating auto-generated sources
Building interpreters for fast_callable
-> First build of interpreters
running build_cython
Enabling Cython debugging support
Updating Cython code

Traceback (most recent call last):
  File "setup.py", line 942, in 
ext_modules = ext_modules)
  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/core.py", line 
151, in setup
dist.run_commands()
  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/dist.py", line 
953, in run_commands
self.run_command(cmd)
  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/dist.py", line 
972, in run_command
cmd_obj.run()
  File "setup.py", line 847, in run
build.run(self)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/distutils/command/build.py", line 
127, in run
self.run_command(cmd_name)
  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/cmd.py", line 
326, in run_command
self.distribution.run_command(command)
  File "/home/king/Sage/git/sage/local/lib/python2.7/distutils/dist.py", line 
972, in run_command
cmd_obj.run()
  File "setup.py", line 370, in run
cache=False,
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 920, in cythonize
aliases=aliases)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 815, in create_extension_list
kwds = deps.distutils_info(file, aliases, base).values
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 670, in distutils_info
return (self.transitive_merge(filename, self.distutils_info0, 
DistutilsInfo.merge)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 680, in transitive_merge
node, extract, merge, seen, {}, self.cimported_files)[0]
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 685, in transitive_merge_helper
deps = extract(node)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 650, in distutils_info0
cimports, externs, incdirs = self.cimports_externs_incdirs(filename)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Utils.py", 
line 44, in wrapper
res = cache[args] = f(self, *args)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 555, in cimports_externs_incdirs
for include in self.included_files(filename):
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Utils.py", 
line 44, in wrapper
res = cache[args] = f(self, *args)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Build/Dependencies.py",
 line 537, in included_files
include_path = self.context.find_include_file(include, None)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Compiler/Main.py",
 line 274, in find_include_file
error(pos, "'%s' not found" % filename)
  File 
"/home/king/Sage/git/sage/local/lib/python2.7/site-packages/Cython/Compiler/Errors.py",
 line 178, in error
raise InternalError(message)
InternalError: Internal compiler error: 'cysignals/signals.px

[sage-devel] Another build error

[Simon King]

Hi!

Building Sage again, I get the error
  InternalError: Internal compiler error: 'cysignals/signals.pxi' not
  found

Unfortunately, the error did not go away after "make distclean".

What can I do? The error occurs on some local branch (different from
develop), however I didn't touch cysignals.

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] Build error

[François Bissey]

OK this looks suspiciously like 
https://bugs.python.org/issue30074
which was fixed by 
https://github.com/python/cpython/pull/1154
which should be in 2.7.14.
What I suspect is happening is that those failures happen when
people upgrade python from 2.7.13 (or older) to 2.7.14.
I have a feeling that when the extension (and there is more than one failing)
is loaded to be tested as being successfully built, the wrong libpython is 
loaded.
Because of our use of rpath, libpython from python 2.7.13 is used and missing 
that particular symbol.
If this is really the case, deleting SAGE_LOCAL/lib/libpython* should be enough
to fix the issue.

François

> On 8/12/2017, at 09:17, Dima Pasechnik  wrote:
> 
> it would be interesting that try to debug this.
> You most probably can get a working version by doing
> 
> make distclean
> 
> (making sure it succeeds!)
> and then building,
> so please do 
> 
> cp -a 
> 
> of the whole tree before doing this...
> 
> 
> -- 
> 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.

Re: [sage-devel] Build error

[Dima Pasechnik]

it would be interesting that try to debug this.
You most probably can get a working version by doing

make distclean

(making sure it succeeds!)
and then building,
so please do 

cp -a 

of the whole tree before doing this...


-- 
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: Why doesn't #23931 get merged?

[Volker Braun]

I'm currently preparing 8.1 which was held up for a while because of some 
last-minute fixes. When that is out we'll be back to the usual pace.

On Thursday, December 7, 2017 at 3:39:07 PM UTC+1, Friedrich Wiemer wrote:
>
> The ticket #23931 has a positive 
> review for quite some time and I'm not aware of any changes left for it, so 
> my humble question is: Is there a reason this ticket isn't merged yet?
> 
>

-- 
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: Why doesn't #23931 get merged?

[William Stein]

On Thu, Dec 7, 2017 at 7:02 AM, Frédéric Chapoton  wrote:
> We have currently 115 such positive-reviewed tickets waiting for inclusion,

Maybe the release manager could use some assistance? Or we could
rotate to more release managers like we used to do for many years...

> see
>
> https://trac.sagemath.org/query?status=positive_review&milestone=!sage-duplicate%2Finvalid%2Fwontfix&group=milestone&col=id&col=summary&col=type&col=component&col=changetime&col=author&col=reviewer&col=dependencies&report=40&desc=1&order=changetime
>
>
> Le jeudi 7 décembre 2017 15:39:07 UTC+1, Friedrich Wiemer a écrit :
>>
>> The ticket #23931 has a positive review for quite some time and I'm not
>> aware of any changes left for it, so my humble question is: Is there a
>> reason this ticket isn't merged yet?
>
> --
> 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.



-- 
William (http://wstein.org)

-- 
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: Why doesn't #23931 get merged?

[Friedrich Wiemer]

OK, so its basically because lack of time?
Is this something a newbie contributer like me can help with?


Am Donnerstag, 7. Dezember 2017 16:02:56 UTC+1 schrieb Frédéric Chapoton:
>
> We have currently 115 such positive-reviewed tickets waiting for 
> inclusion, see
>
>
> https://trac.sagemath.org/query?status=positive_review&milestone=!sage-duplicate%2Finvalid%2Fwontfix&group=milestone&col=id&col=summary&col=type&col=component&col=changetime&col=author&col=reviewer&col=dependencies&report=40&desc=1&order=changetime
>
> Le jeudi 7 décembre 2017 15:39:07 UTC+1, Friedrich Wiemer a écrit :
>>
>> The ticket #23931 has a positive 
>> review for quite some time and I'm not aware of any changes left for it, so 
>> my humble question is: Is there a reason this ticket isn't merged yet?
>> 
>>
>

-- 
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: [OT] Re: Issue with quick start

[Simon King]

On 2017-12-07, Jeroen Demeyer  wrote:
> On 2017-12-02 01:24, d...@shorewestern.com wrote:
>> communicative human nature yearns for
>> abbreviation
>
> My impression is that this is mostly an American phenomenon.

When I did my PhD in Strasbourg, I thought it was a French
phenomenon. Unless you see a clear distinction between an abbreviation
and an acronym.

I often wondered about acronyms written on signs around university.
Once, when I was about to enter the building of IRMA
(clearly: Institut de recherche mathématique avancée, which is also
"known" as UMR 7501), someone asked me for directions. More precisely,
he asked me (translated to English): "Where do I find [some random
combination of letters]?"
So, that guy not only used the acronym in speaking (instead of only
in writing), but he also took it for granted that everybody
understands a random acronym.

In German, we have an abbreviation for "compulsive abbreviation
disorder": Aküfi ("Abkürzungsfimmel", which roughly means
"abbrevimania").

That said, I consider SageMath to be a name.

OT, but anyway...

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: Why doesn't #23931 get merged?

[Frédéric Chapoton]

We have currently 115 such positive-reviewed tickets waiting for inclusion, 
see

https://trac.sagemath.org/query?status=positive_review&milestone=!sage-duplicate%2Finvalid%2Fwontfix&group=milestone&col=id&col=summary&col=type&col=component&col=changetime&col=author&col=reviewer&col=dependencies&report=40&desc=1&order=changetime

Le jeudi 7 décembre 2017 15:39:07 UTC+1, Friedrich Wiemer a écrit :
>
> The ticket #23931 has a positive 
> review for quite some time and I'm not aware of any changes left for it, so 
> my humble question is: Is there a reason this ticket isn't merged yet?
> 
>

-- 
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] Why doesn't #23931 get merged?

[Friedrich Wiemer]

The ticket #23931 has a positive 
review for quite some time and I'm not aware of any changes left for it, so 
my humble question is: Is there a reason this ticket isn't merged yet?


-- 
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] [OT] Re: Issue with quick start

[Jeroen Demeyer]

On 2017-12-02 01:24, d...@shorewestern.com wrote:

communicative human nature yearns for
abbreviation


My impression is that this is mostly an American phenomenon.

Off-topic true story: when I was a young PhD student, I spent a few 
weeks in Berkeley (California, USA). While walking to the university 
campus, I passed a road marking saying "XING PED" (see also 
https://xkcd.com/781/). Every day I passed there and I couldn't figure 
out what it meant. Until at some point I understood that it meant 
"pedestrian crossing".


--
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: Issue with quick start

[Jeroen Demeyer]

On 2017-12-04 23:52, Dima Pasechnik wrote:

I will open a trac ticket changing Math* to Wiskunde.


Great idea!

--
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] Build error

[Jeroen Demeyer]

On 2017-12-07 15:13, Simon King wrote:

How to fix that?


This is a bug that several people have reported but I don't know how to 
reproduce it.



make distclean and start again?


That works.

--
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] Build error

[Simon King]

Hi!

On a laptop that I haven't used for a while, I tried to upgrade Sage.
I.e., I did "git checkout develop", "git pull" and "make".

While building python2-2.7.15.p2, I get
  [python2-2.7.14.p2] ImportError: No module named _ctypes
  [python2-2.7.14.p2] ctypes module failed to import

and

  [python2-2.7.14.p2] Python build finished, but the necessary bits to
  build these modules were not found:
  [python2-2.7.14.p2] _bsddb _tkinter   bsddb185
  [python2-2.7.14.p2] dbmdl gdbm
  [python2-2.7.14.p2] imageopsunaudiodev
  [python2-2.7.14.p2] To find the necessary bits, look in setup.py in
  detect_modules() for the module's name.
  [python2-2.7.14.p2] 
  [python2-2.7.14.p2] 
  [python2-2.7.14.p2] Failed to build these modules:
  [python2-2.7.14.p2] _ctypes_elementtree
  _multiprocessing
  [python2-2.7.14.p2] array  mmap   

How to fix that? make distclean and start again?

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.