-
-
Notifications
You must be signed in to change notification settings - Fork 561
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
Fix docstring failures in designs.balanced_incomplete_block_design with use_LJCR=True #30107
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
Branch: u/gh-Ivo-Maffei/bibd_LJCR_fix |
comment:2
I tried looking for an entry in the LJCR database that gets used by Sage, but I can't find one.
where I changed the I didn't obtain any results. So I think that the LJCR database is actually never used. On a side note, to fix the New commits:
|
comment:3
to see the errors (before this branch), run
In particular I see
|
comment:4
With your branch, all the tests as in comment:3 pass. However, I can revert your change https->http as follows and still have all the tests pass. --- a/src/sage/combinat/designs/covering_design.py
+++ b/src/sage/combinat/designs/covering_design.py
@@ -521,7 +521,7 @@ def best_known_covering_design_www(v, k, t, verbose=False):
k = int(k)
t = int(t)
param = "?v=%s&k=%s&t=%s" % (v, k, t)
- url = "http://ljcr.dmgordon.org/cover/get_cover.php" + param
+ url = "https://ljcr.dmgordon.org/cover/get_cover.php" + param
if verbose:
print("Looking up the bounds at %s" % url)
It appears that in your Sage's python URLlib is broken. Of course it should be able to handle https. Tell me more about your |
Reviewer: Dima Pasechnik |
comment:5
Is this otherwise ready for review? |
comment:6
I'm not sure where the python software I have comes from.
Actually the full traceback when I get the
So it seems the issues lies in the python shipped with sage. Apart from the above, I would like to substitute the parameters of the docstring test as at the moment they are not testing the LJCR database. However, I can't find any set of parameters for which the LJCR database is actually used by sage. |
comment:7
Seems you built or installed Sage without OpenSSL. |
comment:8
I use macOS which ships with LibreSSL and sort of "redirect" all OpenSSL commands to LibreSSL, i.e.
I looked back at the installation guide (https://doc.sagemath.org/html/en/installation/source.html#prerequisites) and it seems that OpenSSL is recommended but not strictly required. If OpenSSL is actually required (as it seems in this case), then the installation guide should be changed. |
comment:9
We have had long discussions on OpenSSL, you can check sage-devel... Well, thanks to Apple for breaking Python on macOS, what can I say. You can install Homebrew Python3, so it will live in /usr/local, Anyhow, just revert the change https->http, so that I can set this ticket to positive review. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
lgtm |
comment:13
Some more suggestions if you care. Otherwise just set back to positive review. Remove this commented-out print (debugging leftover?)
Remove space before question mark:
Add space around
Use f-strings and lowercase.
|
comment:14
After the class |
comment:16
I fixed the suggested formatting and rebased the branch on 9.2.beta5 |
comment:17
Looks good to me if the patchbot is happy. |
Changed reviewer from Dima Pasechnik to Dima Pasechnik, Samuel Lelièvre |
comment:18
Regarding OpenSSL for Sage on macOS, you can fix |
comment:19
Bots are happy. Positive review. Regarding the minor warnings:
|
comment:20
The "multiple statements on one line" are fixed at #30131. |
This comment has been minimized.
This comment has been minimized.
Dependencies: 30131 |
Changed dependencies from 30131 to #30131 |
comment:23
I merged the tickets because there was a merge conflict |
comment:24
coudln't
be simplified to
? |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:26
OK, good |
Changed branch from u/gh-Ivo-Maffei/bibd_LJCR_fix to |
The use of
use_LJCR=True
indesigns.balanced_incomplete_block_design
give rise to few issues.IncidenceStructure
instead ofBalancedIncompleteBlockDesign
ValueError
exception can be raised if the parameters searched are not in the databaseExample for 2:
In addition to the above, the docstring tests that are meant to test the use of
use_LJCR=True
are not actually testing the LJCR online database.Depends on #30131
CC: @dimpase
Component: combinatorial designs
Keywords: bibd, LJCR
Author: Ivo Maffei
Branch/Commit:
39e147b
Reviewer: Dima Pasechnik, Samuel Lelièvre
Issue created by migration from https://trac.sagemath.org/ticket/30107
The text was updated successfully, but these errors were encountered: