Changes between Initial Version and Version 1 of Ticket #30184


Ignore:
Timestamp:
Feb 12, 2019, 4:48:37 PM (6 years ago)
Author:
Dan Davis
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30184 – Description

    initial v1  
    11By default, Windows terminals start with code page 437, which is roughly equivalent to ASCII.   While working on #30178, I discovered that this causes the following traceback:
    22
    3 ```
     3{{{
    44(mplusmon) λ manage.py runserver
    55Watchman unavailable: pywatchman not installed.
     
    2020    return codecs.charmap_encode(input,self.errors,encoding_map)[0]
    2121UnicodeEncodeError: 'charmap' codec can't encode character '\u2026' in position 24: character maps to <undefined>
    22 ```
     22}}}
    2323
    24 The problem can be resolved by changing the code page to UTF-8, as follows:
     24A workaround is to change the code page to UTF-8, as follows:
    2525
    26 ```
     26{{{
    2727chcp 65001
    28 ```
     28}}}
    2929
    30 This appears to be a new issue relative to Django 2.1.7, because the problem did not occur there.    I'll track down wherever someone entered the horizontal elipsis character rather than "..." into the code, because this ought to be easy enough to fix.
     30This appears to be a new issue relative to Django 2.1.7, because the problem did not occur there.    I'll track down wherever someone entered the horizontal elipsis character rather than "..." into the code, because this ought to be easy enough to fix.   Whomever did this was probably not even aware of it and it has worked well enough since almost all Django developers will use MacOS or Linux.
Back to Top