New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade cypari2 package #23518
Comments
comment:1
any release coming soon ? |
comment:3
ping ? this is the current blocking point in my experimental python3 build. |
comment:5
I don't really know about what kind of automated stuff happens on trac anymore, so let me ask this perhaps naive question: why is this a block for anything? I only created this ticket because of #15829 which itself is still under development (has never even been marked as "needs review"). |
comment:6
Sorry, I have used your ticket for my own purposes. I need (for something having to do with making sage works with python3) to have a new release of cypari2. So I would just embark in this ticket, which is also asking for a release of cypari2. |
comment:7
Aha! I understand now. It may be worth updating the ticket description: it might encourage people to work on this ticket! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
Commit: |
comment:14
Something very strange happens while testing the package:
This happens only when testing the Sage package. Any other way of running the testsuite works fine. I have absolutely no idea why and I hope that somebody else can fix it. New commits:
|
comment:15
How can I run this testsuite ? |
comment:16
The failing testsuite is But like I said, the strange thing is that manually running |
comment:17
I can confirm the failure of How can I run manually "spkg-check" ? |
comment:18
wiht python3-sage, I get something else
|
comment:19
Can I please have
|
comment:20
Sorry, I do not understand.. EDIT: oh, some kind of joke ? |
comment:21
Yes, a joke of course. Let me just say that I'm not a fan of the way how Python deals with unicode encoding issues... |
comment:22
OK, the issues are due to |
comment:23
I just saw your e-mail about this. Did you figure it out? You mentioned something about |
comment:24
Replying to @embray:
Yes. The issue is that Python's
It turns out that cypari2 was assuming that files were opened in UTF-8 mode. I now made this explicit with |
This comment has been minimized.
This comment has been minimized.
comment:25
By the way, this is a useful guide handling encodings when reading text files: I would suggest also adding |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:27
Replying to @embray:
This is not applicable here. In this case, we know that all the files we deal with are UTF-8. The input files come from the PARI documentation which is written in UTF-8. And the output files contain auto-generated Cython code which has a |
comment:28
This version builds and passes its testsuite. I did not yet run Sage doctests. |
comment:29
That's good, that makes it easy then. |
comment:30
Side comment: the |
comment:31
not yet smooth for python3:
|
comment:32
Sigh... but Python 3 works fine outside of Sage in Travis CI, running the same commands ( |
comment:33
Well, I am using "export SAGE_PYTHON3=yes", pull the branch here and "sage -c -f cypari" (in a dedicated sage install for py3 experimental work) Maybe it is because the python3 general setup is not firmly in place.. |
comment:34
Doctests pass (on Python 2). I don't understand why this fails with In any case, I suggest that this should not be a blocker for merging this ticket. It doesn't make the Python 3 situation any worse than before and it helps people who need to update |
comment:35
ok, ok. But still, if somebody could try to reproduce that error that I find.. EDIT: I do not have a particular setup, I think. |
comment:36
I'll have a look at the Python 3 issue. I agree with Jeroen it needn't hold up this issue but I can try to investigate ASAP (I need to do a |
comment:37
ok, let this go in. We will see later what to do for tests to pass in python3. |
Reviewer: Frédéric Chapoton |
Changed branch from u/jdemeyer/upgrade_cypari2_package to |
comment:39
Any news from the |
Changed commit from |
comment:40
Not an answer on the cypari2 relation to python3.. Well, this ticket fixes the issue that I had. One of the first blocking point for PYTHON3 is now the division problem in #22875. If you feel like handling this one, it would be great, because I do not understand exactly what you ask for there. And #23785 would be helpful too. |
Tarball: https://pypi.python.org/packages/1c/ff/a9a0c9087c08d14807214930bed13ccfb6b2198f38c6992d89c63eb5870b/cypari2-1.1.1.tar.gz
CC: @jdemeyer @defeo @videlec @kiwifb
Component: packages: standard
Keywords: cypari2, sd87
Author: Jeroen Demeyer
Branch:
749c534
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/23518
The text was updated successfully, but these errors were encountered: