JuliaPy / JuliaPy/PythonCall.jl
print versus println to stdout
- Vorherrschende Sprache
- Julia
- Sterne
- 1.1k
- Forks
- 86
- Ø Merge
- 1 T. 22 Std.
- Gemergte PRs (30 T.)
- 3
Beschreibung
In transitioning from PyCall.jl, I was just trying to confirm that the stdout forwarding worked similarly and came across an example I found puzzling.
```
@py begin
import numpy as np
a = np.zeros(10)
println(a)
end
```
Completes and prints as normal
```
@py begin
import numpy as np
a = np.zeros(10)
print(a)
end
```
Fails and gives the error "Python: TypeError: memoryview: a bytes-like object is required, not 'str'".
I am just trying to reproduce the functionality I had before with py_str and using the `pyimport("sys")."stdout" = PyTextIO(stdout)`. My concern is that sometimes I want to import and run python packages that are doing print and not println and would like that to work without me having to edit them. Is this expected behavior or have I done something wrong/there is a better way to be going about this?
```
Julia Version 1.8.2
Commit 36034abf260 (2022-09-29 15:21 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
[6099a3de] PythonCall v0.9.12
```
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start by reproducing the two @py examples with PythonCall v0.9.12, focusing on stdout forwarding and the PyTextIO setup described in the issue. Trace how print and println are handled, then verify that Python packages using print forward output without the reported memoryview TypeError.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- julia, python
- Bereich
- api, backend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100