Skip to content
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

Improve coverage test for structure/element.pyx #10779

Closed
sagetrac-ejeanvoi mannequin opened this issue Feb 14, 2011 · 33 comments
Closed

Improve coverage test for structure/element.pyx #10779

sagetrac-ejeanvoi mannequin opened this issue Feb 14, 2011 · 33 comments

Comments

@sagetrac-ejeanvoi
Copy link
Mannequin

sagetrac-ejeanvoi mannequin commented Feb 14, 2011

Improve coverage test for structure/element.pyx

Status as of Sage 6.2.beta4:

SCORE src/sage/structure/element.pyx: 27.5% (42 of 153)

with patch:

SCORE src/sage/structure/element.pyx: 32.7% (50 of 153)

Component: doctest coverage

Author: Emmanuel Jeanvoine, Frédéric Chapoton

Branch/Commit: dbf722e

Reviewer: Nathann Cohen, Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/10779

@sagetrac-ejeanvoi sagetrac-ejeanvoi mannequin added this to the sage-5.11 milestone Feb 14, 2011
@sagetrac-ejeanvoi
Copy link
Mannequin Author

sagetrac-ejeanvoi mannequin commented Feb 14, 2011

Added some doctests

@KPanComputes
Copy link

comment:1

Attachment: trac_10779-doctests.patch.gz

@KPanComputes

This comment has been minimized.

@KPanComputes
Copy link

comment:2

Hello!

  • Please refer to the conventions page for how to write in ReST markup. For instance, you need a blank line after :: for getting verbatim environment. Also, please note that, a verbatim environment is preceded by ::.

  • It'd be nice if you also go ahead and add more doctests. Also, please correct the docstrings formatting whenever you can -- like codifying self, True and such by using two backticks...

  • Major: "ERROR: Please add a TestSuite(s).run() doctest."

Hoping to hear from you soon...

Cheers, Kannappan.

@fchapoton

This comment has been minimized.

@fchapoton
Copy link
Contributor

replaces previous patch

@fchapoton
Copy link
Contributor

comment:5

Attachment: trac_10779-doctests-v2.patch.gz

apply only trac_10779-doctests-v2.patch

@fchapoton
Copy link
Contributor

Commit: c84246e

@fchapoton
Copy link
Contributor

New commits:

c84246e#10779: Improve coverage test for structure/element.pyx

@fchapoton
Copy link
Contributor

Branch: u/chapoton/10779

@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 27, 2014

Changed commit from c84246e to db023d4

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 27, 2014

Branch pushed to git repo; I updated commit sha1. New commits:

db023d4Merge branch 'u/chapoton/10779' of ssh://trac.sagemath.org:22/sage into 10779

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 27, 2014

Changed commit from db023d4 to 2e30025

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Aug 20, 2014

Branch pushed to git repo; I updated commit sha1. New commits:

9d72c81Merge branch 'u/chapoton/10779' of ssh://trac.sagemath.org:22/sage into 10779
9531937trac #10779 correct failing doctest + more doc changes

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Nov 15, 2014

Branch pushed to git repo; I updated commit sha1. New commits:

54396cdMerge branch 'u/chapoton/10779' into 6.4

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Nov 15, 2014

Changed commit from 9531937 to 54396cd

@nathanncohen
Copy link
Mannequin

nathanncohen mannequin commented Jan 16, 2015

comment:16

Hello !

This code seems good, but I do not understand the three functions lcm,gcd, and now (with your branch) xgcd in element.pyx. Isn't it more reasonable to import them from sage.ring.arith instead ? (a lazy import if that was the problem)

Nathann

@fchapoton
Copy link
Contributor

comment:17

xgcd was already there. This branch only changes the doc.

@nathanncohen
Copy link
Mannequin

nathanncohen mannequin commented Jan 16, 2015

comment:18

Oh sorry, I made this mistake by reading the diff file.

Okay let's go.

Nathann

@nathanncohen
Copy link
Mannequin

nathanncohen mannequin commented Jan 16, 2015

Reviewer: Nathann Cohen

@jdemeyer
Copy link

comment:20
It is especially important to
keep this in mind whenever you move a class down from Python to
Cython.

Is this really true? I think Cython is just following the Python convention here...

@jdemeyer
Copy link

comment:21

The tests for gcd, lcm and xgcd do not actually test the functions from element.pyx.

@nathanncohen
Copy link
Mannequin

nathanncohen mannequin commented Jan 16, 2015

comment:22

The tests for gcd, lcm and xgcd do not actually test the functions from element.pyx.

It's true. Do we create a patch to remove them and import the actual ones ? It's probably only to avoid a direct import.

Nathann

@jdemeyer
Copy link

Changed branch from u/chapoton/10779 to u/jdemeyer/ticket/10779

@jdemeyer
Copy link

Changed reviewer from Nathann Cohen to Nathann Cohen, Jeroen Demeyer

@jdemeyer
Copy link

New commits:

dbf722eRemove gcd, lcm, xgcd from element.pyx

@jdemeyer
Copy link

Changed commit from 54396cd to dbf722e

@nathanncohen
Copy link
Mannequin

nathanncohen mannequin commented Jan 18, 2015

comment:25

Passes all long tests, does the job.

Nathann

@fchapoton fchapoton modified the milestones: sage-6.4, sage-6.5 Jan 23, 2015
@vbraun
Copy link
Member

vbraun commented Jan 23, 2015

Changed branch from u/jdemeyer/ticket/10779 to dbf722e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants