-
Notifications
You must be signed in to change notification settings - Fork 201
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
Browse box problem #510
Comments
In the refactor branch, this is not fixed, but it is now a ValueError: invalid literal for int() with base 10: 'r'. |
This issue actually refers to the browse box (there is no search box yet). |
After looking at this I have the strong opinion that it should NOT be fixed except by replacing all the custom parsing functions used to process the form input by central standardised ones. |
The new parsing functions have not been applied for classical modular forms yet. So these errors do still occur. |
If I knew how to apply the new parsing functions I would do that but they seem to be completely undocumented and I can't figure out how to use them or if they are even in a state that they could be used. |
This is fixed as of PR #1465 (possibly earlier), closing. |
When you put something inappropriate into a search box, instead of letting you know as in the elliptic curves page, it gives a server error.
http://beta.lmfdb.org/ModularForm/GL2/Q/holomorphic/ranges?level=r&weight=&character=0&Submit=Search
gives a TypeError: coercing to Unicode: need string or buffer, int found
The text was updated successfully, but these errors were encountered: