Quote from: xnova on February 03, 2014, 02:23:14 AM

Quote from: Asterios on February 03, 2014, 12:58:34 AM

Quote from: PhantomPhreak on February 03, 2014, 12:45:46 AM

Quote from: Asterios on February 03, 2014, 12:37:51 AM

Quote from: PhantomPhreak on February 03, 2014, 12:24:00 AM

Quote from: PhantomPhreak on February 02, 2014, 11:20:47 PM

Quote from: Asterios on February 02, 2014, 10:57:15 PM

I am getting another error in the "market". What anyone else?

Code:

Feeds
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 661, i
n
   market(args.give_asset, args.get_asset)
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 79, in
market
   print(str(table))
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 34, in write
   self.__convertor.write(text)
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 115, in write
   self.write_and_convert(text)
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 142, in write_and_convert
   self.write_plain_text(text, cursor, len(text))
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 147, in write_plain_text
   self.wrapped.write(text[start:end])
  File "C:\counterpartyd_build\env\lib\encodings\cp850.py", line 19, in encode
   return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2026' in position
693: character maps to

The Windows terminal has trouble with Unicode. I'll try to write a workaround.

There's a partial fix in the master branch now. I don't have a Windows computer, however, so it's pretty much untested. Let me know if it works!

No, sorry PhantomPhreak. It is not working. Here is the error message:

Code:

Feeds
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 667, i
n
   market(args.give_asset, args.get_asset)
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 86, in
market
   print_(str(table))
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 33, in
print_
   print(foo.encode('utf-8').decode('latin-1'))
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 34, in write
   self.__convertor.write(text)
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 115, in write
   self.write_and_convert(text)
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 142, in write_and_convert
   self.write_plain_text(text, cursor, len(text))
  File "C:\counterpartyd_build\env\lib\site-packages\colorama\ansitowin32.py", l
ine 147, in write_plain_text
   self.wrapped.write(text[start:end])
  File "C:\counterpartyd_build\env\lib\encodings\cp850.py", line 19, in encode
   return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\x80' in position 69
4: character maps to

Even the run.py wallet is not working anymore (was working before). Error:

Code:

C:\counterpartyd_build>run.py wallet
Traceback (most recent call last):
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 634, i
n
print_()
TypeError: print_() takes exactly 1 argument (0 given)

I guess that your best bet is to use an old version for now. xnova usually handles the Windows support, and he should be able to fix the issue soon.

I've reverted that commit, of course.

Ok, No problem. I can wait

Thanks for the fast help.

I am rebuilding my windows environment so I can try to reproduce this. I suspect this is another unicode handling issue (cmd.exe has issues handling unicode).

At the dos prompt, try running the "powershell" command, and then launching counterpartyd. See if that fixes it.

It is. I put back in the Unicode ellipses. We probably should wrap the logger and print() with something that converts to another encoding. (Removing the ellipses isn't a solution, because broadcasts include arbitrary UTF-8 strings.)