seems like we look at a tip of py2/3 string/unicode iceberg mess... :-)
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com
IMHO thats a bug that we should report to pip upstream... can you do that
with your distribution details?
On Saturday, August 18, 2018 at 9:15:04 PM UTC+2, Luis Finotti wrote:
>
>
>
> On Saturday, August 18, 2018 at 4:58:39 AM UTC-4, Volker Braun wrote:
>>
>> pip chokes on parsing /etc/$DISTRO-r
On Saturday, August 18, 2018 at 4:58:39 AM UTC-4, Volker Braun wrote:
>
> pip chokes on parsing /etc/$DISTRO-release (for whatever Linux $DISTRO you
> are yousing). Please post the file content.
>
Good catch! Indeed, that file had UTF-8 characters. Removing them
resulted in a successful buil
pip chokes on parsing /etc/$DISTRO-release (for whatever Linux $DISTRO you
are yousing). Please post the file content.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an ema
On Friday, August 17, 2018 at 5:42:42 AM UTC+3, vdelecroix wrote:
>
> On 8/15/18 5:05 PM, Dima Pasechnik wrote:
> > besides it's being gcc 8.2, and AFAIK nobody ever built Sage with gcc 8
>
> This is perfectly fine with gcc-8.2.0 that I have on my machine. And
> building Sage with it since lon
https://github.com/sagemath/sage/releases/tag/8.4.beta1
Le 16/08/2018 à 18:14, Luis Finotti a écrit :
I'm sorry to have to ask, but could you tell me how to get 8.4beta1
source?
On Thursday, August 16, 2018 at 6:41:43 AM UTC-4, Dima Pasechnik wrote:
the latest beta, 8.4beta1, updates pip
On 8/15/18 5:05 PM, Dima Pasechnik wrote:
besides it's being gcc 8.2, and AFAIK nobody ever built Sage with gcc 8
This is perfectly fine with gcc-8.2.0 that I have on my machine. And
building Sage with it since long now. I don't see any reason to
switch to another compiler.
--
You received thi
you can clone
https://github.com/sagemath/sage.git
and then checkout 'develop' branch.
This is where the latest beta/release candidate is normally mirrored.
On Thursday, August 16, 2018 at 7:14:17 PM UTC+3, Luis Finotti wrote:
>
> I'm sorry to have to ask, but could you tell me how to get 8.4be
I'm sorry to have to ask, but could you tell me how to get 8.4beta1 source?
On Thursday, August 16, 2018 at 6:41:43 AM UTC-4, Dima Pasechnik wrote:
>
> the latest beta, 8.4beta1, updates pip package.
> it's the way to go anyway.
--
You received this message because you are subscribed to the Goog
the latest beta, 8.4beta1, updates pip package.
it's the way to go anyway.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.
perhaps it even suffices to insert prints in appropriate places in local/
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.c
well, you can try debugging it. Modify pip tarball in upstream/, update its
checksum, run sage -i pip, rinse and repeat...
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an
On Wednesday, August 15, 2018 at 6:05:04 PM UTC-4, Dima Pasechnik wrote:
>
> To switch to non-default C/C++ compiler, you need to run
>
> ./configure CC=gcc-7 CXX=g++-7
>
> and most probably
>
> make distclean
>
> before starting the build
>
>
Thanks for your continued support! Unfornuately, GCC
To switch to non-default C/C++ compiler, you need to run
./configure CC=gcc-7 CXX=g++-7
and most probably
make distclean
before starting the build
On Thursday, August 16, 2018 at 12:53:16 AM UTC+3, Luis Finotti wrote:
>
>
>
> On Wednesday, August 15, 2018 at 5:14:47 PM UTC-4, Dima Pasechnik
On Wednesday, August 15, 2018 at 5:14:47 PM UTC-4, Dima Pasechnik wrote:
>
> [pip-9.0.3] File
> "/usr/local/sage-8.3/local/lib/python3.6/encodings/ascii.py", line 26, in
> decode
> [pip-9.0.3] return codecs.ascii_decode(input, self.errors)[0]
>
> This is actually strange - why is it pytho
[pip-9.0.3] File
"/usr/local/sage-8.3/local/lib/python3.6/encodings/ascii.py", line 26, in
decode
[pip-9.0.3] return codecs.ascii_decode(input, self.errors)[0]
This is actually strange - why is it python3.6?
Are you trying to build a python3-based Sagemath?
(python3 support is very much wo
besides it's being gcc 8.2, and AFAIK nobody ever built Sage with gcc 8, I
don't see anything strange.
Not sure what data pip installer is choking on here. Hostnames with
non-ascii chars?
On Wednesday, August 15, 2018 at 4:24:01 PM UTC+3, Luis Finotti wrote:
>
> It seems that the terminal outpu
It seems that the terminal output was cut. Here it is in full:
https://pastebin.com/6gxaxc7P
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsub
Thanks for the prompt reply. I tried your suggestion but it failed. Here's
the screen capture form it:
make build/make/Makefile --stop
make[1]: Entering directory `/home/leo/mysagemath/SageMath'
rm -f config.log
mkdir -p logs/pkgs
ln -s logs/pkgs/config.log config.log
running CONFIG_SHELL=/bin/bash
one can see in your log:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 16:
ordinal not in range(128)
this suggests non-ascii chars in some of your paths, or something "interesting"
with your locale.
Can you try running
LC_ALL=C ./sage -i pip
to see if this succeeds.
-
Thanks for the reply!
On Tuesday, August 14, 2018 at 5:22:31 PM UTC-4, Dima Pasechnik wrote:
>
> as you see at the end of the message:
> log file: /usr/local/sage-8.3/logs/pkgs/pip-9.0.3.log
>
> please attach it.
>
>
Done. Let me know if you have any suggestions...
--
You received this message
as you see at the end of the message:
log file: /usr/local/sage-8.3/logs/pkgs/pip-9.0.3.log
please attach it.
On Tuesday, August 14, 2018 at 9:16:14 PM UTC+3, Luis Finotti wrote:
>
> I've just tried to compile sage 8.3 from source on Debian Sid/Unstable. I
> don't see much in the screen right b
22 matches
Mail list logo