-
Notifications
You must be signed in to change notification settings - Fork 6
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
Extraneous blank line printed to terminal on import. #30
Comments
Using debug mode in VS Code Version 1.82.2, the extra line is being created at import by the call to: This call to Would adding a context manager (like |
@dwr-zroy Did you try the redirect stdout as you suggest above? If this is happening in the C/Fortran libraries then it is unlikely that python level redirection would work. Let me know if that works. |
No I had not. I tested and that option didn't work as it was only redirecting the python level The solution below uses the smallest context managers I could drum up to accomplish the change with as little risk of modifying I think a drawback to this solution is it's pretty verbose, and it is only used once. Additionally, I haven't explored whether or not errors raised in Branch on my fork for reference
|
1.1.6
, Buildpy39_0
Python 3.9.16
Windows 10
, Build19045.3324
,64 bit x86
Description
On import, the module prints a blank line to the terminal. Not typically an issue, but when module is imported in subprocesses, each import creates a new blank line on the terminal.
What I Did
Output
In a CMD window, I ran the following commands, and received the following outputs. Note the lack of a blank line between the other expressions.
The text was updated successfully, but these errors were encountered: