-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Update gmpy2 package #22927
Comments
comment:3
Note that gmpy2 was already an optional package. The title and description of the ticket are not be appropriate. New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to jsb++ |
Changed keywords from jsb++ to thursdaysbdx |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
The version in the snapshot's setup.py was incorrect. https://www.labri.fr/perso/vklein/gmpy2-snapshot-02.05.17.tar.gz ans checksum.ini have been updated |
comment:13
See gmpy pull request #134 for making |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:16
New snapshot version gmpy2-snapshot-22.05.17.tar.gz, checksum has been updated. |
This comment has been minimized.
This comment has been minimized.
comment:19
Why the change in component? If you want to make it standard, it should be discussed on |
comment:32
Update snapshot version to gmpy2-snapshot-23.06.17.tar.gz |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Replying to @vinklein:
In that case, I'm not sure whether the package can be accepted. At a minimum, could you add a patch to disable the failing tests, such that Second, you should better document how you obtained this tarball. Posting a tarball on your personal home page without further explanation is not sufficient. Is there any chance you could convince upstream to make a proper release? That would of course be much better. Note that you have never set this ticket to needs_review. If you want this to be merged in Sage, you'll need to do that. |
This comment has been minimized.
This comment has been minimized.
comment:35
Our goal has always be to have a proper release of gmpy2. It look like things are progressing well these last weeks. You can look at issue #146 if you want more specifics. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:37
update package version to gmpy2-snapshot-14.11.17.tar.gz |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:39
rebase on 8.1.rc0 and squash commit |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
This comment has been minimized.
This comment has been minimized.
Reviewer: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
comment:44
Running |
comment:45
(me too (running ptestlong)) |
comment:47
Replying to @videlec:
good for me! |
Changed branch from u/vklein/add_gmpy2_as_an_optional_package to |
Update gmpy2 package to have access to the gmpy2 C API.
Tarball : gmpy2-2.1.0a1.tar.gz
This gmpy2 version provides a Cython interface.
CC: @videlec
Component: packages: optional
Keywords: thursdaysbdx
Author: Vincent Klein
Branch/Commit:
e000563
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/22927
The text was updated successfully, but these errors were encountered: