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

Impossible to put a semi-colon in commands= entry #33

Closed
pytoxbot opened this issue Sep 17, 2016 · 3 comments
Closed

Impossible to put a semi-colon in commands= entry #33

pytoxbot opened this issue Sep 17, 2016 · 3 comments

Comments

@pytoxbot
Copy link

@pytoxbot pytoxbot commented Sep 17, 2016

The official way to run the numpy testsuite is:

python -c 'import numpy; numpy.test()'

However, if I put that in a commands= entry, then the ; is treated as starting a comment, and there is no possible way to escape it. I guess technically this is a py.iniparser bug, but there it is.

@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by @hpk42

you can try it out via "pip install -i http://pypi.testrun.org -U pytest"
(and sorry it took a while)

@pytoxbot pytoxbot closed this Sep 17, 2016
@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by @hpk42

fix issue33 - commentchars in key-value sections are ignored or to put it positively,
commentchars need to start the lstripp()ed line to have them ignored

→ <<cset 5e7a89186ac5>>

@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by @hpk42

Hum, unfortunate. I think we added ";" for compatibility-to-ini-parsing reasons. Not sure how to best fix the issue at the moment. As they are probably not too many users of py.iniparser we are probably free to change parsing semantics a bit.

@tox-dev tox-dev locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant