Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2001-June/015621.html below:

[Python-Dev] Unicode fallout: Windows _winreg project broken

• Previous message: [Python-Dev] Unicode fallout: Windows _winreg project broken
• Next message: [Python-Dev] New Unicode warnings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

martin wrote:


> > IOW, HAVE_USABLE_WCHAR_T no longer gets #define'd on Windows, and
> > that prevents unicodeobject.c from supplying routines _winreg.c
> > calls.
> 
> The best thing, IMO, would be if PC/config.h defines everything
> available in config.h also. In this case, the proper defines would be
> 
> #define Py_USING_UNICODE
> #define HAVE_USABLE_WCHAR_T
> #define Py_UNICODE_SIZE 2
> #define PY_UNICODE_TYPE wchar_t
> 
> If that approach is used, the defaulting in Include/unicodeobject.h
> could go away.

my fault; I missed the HAVE_USABLE_WCHAR_T define when I tried
to fix tim's fix.

I'll fix it.

</F>

• Previous message: [Python-Dev] Unicode fallout: Windows _winreg project broken
• Next message: [Python-Dev] New Unicode warnings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4