New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ebcdic compliancy in stringobject source #36617
Comments
the printable character set test made inside |
Logged In: YES Is it really worth fixing this? Python assumes that the |
Logged In: YES when porting to OS390(EBCDIC os) , the only place I found On the second topic using a C library function I am 100% ok
the only question is that I am persuaded that using for
instance the isascii XPG C function will generate more
complex and slower code when trying to keep it in
compliancy both with EBCDIC/ASCII targets. Having a more
generic #define like :
#define EBCDIC inside the config.h set by ./configure when
platform is EBCDIC is IMO the best compromise here. |
Logged In: YES I believe there are a number of places where the code |
Logged In: YES I am still 100% with you on that ,my only remark here is that After that when the basic kernel is up in EBCDIC mode you'll |
Logged In: YES The last attached diff files contains a more robust patch by |
Logged In: YES Modifying pyconfig.h.in (alone) is a mistake: this is a When producing patches, please produce a single file I'm still opposed to singling-out a specific encoding; |
Logged In: YES I look at the approach taken in patch bpo-479898 , looks fine It works well and is definitivelly the best approach for the I looked also at the PRINT_MULTIBYTE_STRING approach based |
Logged In: YES This is an ugly patch, |
Logged In: YES
If you look at my answer dated 2002-06-02 , I indicated that |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: