OK, I have an idea of what might be going on here – my guesses are either that you are running within an IDE that is fouling up an assumption in PyUtilib.subprocess, or else a UNICODE issue in python 3.4 that is fouling up the output processing in pyutilib.subprocess when we are streaming output. By chance, is your computer set up to use a non-ASCII (or non-UTF-8) character set by default (i.e., set up for a non-English locale)?
1) A potential workaround (and this is really a shot in the dark): try adding the following to the top of your script:
import sys
reload(sys)
sys.setdefaultencoding(‘utf-8’)
2) Let’s try actually fixing the root problem… can you tell us:
a. what OS?
b. is your computer set up to run in either a language other than English or a locale other than en_US?
c. what version of Pyomo (run “pyomo --version” at the command line and share the output)?
d. are you running in some form of a debugger or IDE?
e. can you share the script fragment that is running the solver (e.g, the lines starting with “opt = SolverFactory” through the actual call to opt.solve)?
Resolving the issue in PyUtilib may take some work (the core PyUtilib developers all develop in the en_US locale, and testing other locales is a bit challenging).
john
--
You received this message because you are subscribed to the Google Groups "Pyomo Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
pyomo-forum...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.