Skip to content
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

unknown encoding -> MemoryError #38866

Closed
quiver mannequin opened this issue Jul 17, 2003 · 2 comments
Closed

unknown encoding -> MemoryError #38866

quiver mannequin opened this issue Jul 17, 2003 · 2 comments
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs)

Comments

@quiver
Copy link
Mannequin

quiver mannequin commented Jul 17, 2003

BPO 772896

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:

assignee = None
closed_at = <Date 2005-10-02.01:52:14.000>
created_at = <Date 2003-07-17.10:27:42.000>
labels = ['interpreter-core']
title = 'unknown encoding -> MemoryError'
updated_at = <Date 2005-10-02.01:52:14.000>
user = 'https://bugs.python.org/quiver'

bugs.python.org fields:

activity = <Date 2005-10-02.01:52:14.000>
actor = 'nnorwitz'
assignee = 'anthonybaxter'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2003-07-17.10:27:42.000>
creator = 'quiver'
dependencies = []
files = []
hgrepos = []
issue_num = 772896
keywords = []
message_count = 2.0
messages = ['17095', '17096']
nosy_count = 3.0
nosy_names = ['nnorwitz', 'anthonybaxter', 'quiver']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue772896'
versions = ['Python 2.3']

@quiver
Copy link
Mannequin Author

quiver mannequin commented Jul 17, 2003

If you try to install a program and one of the files
declares an unknown encoding(like 'UFT-8'),
byte-compiling the file fails and get the message, "Sorry:
MemoryError: ()"

This message obscures the problem and makes it difficult
to spot the problem.
In fact, it took me a while to find out that the unknown
encoding declaration caused the trouble.

The error message needs to be more explicit.

@quiver quiver mannequin closed this as completed Jul 17, 2003
@quiver quiver mannequin assigned anthonybaxter Jul 17, 2003
@quiver quiver mannequin added the interpreter-core (Objects, Python, Grammar, and Parser dirs) label Jul 17, 2003
@quiver quiver mannequin closed this as completed Jul 17, 2003
@quiver quiver mannequin assigned anthonybaxter Jul 17, 2003
@quiver quiver mannequin added the interpreter-core (Objects, Python, Grammar, and Parser dirs) label Jul 17, 2003
@nnorwitz
Copy link
Mannequin

nnorwitz mannequin commented Oct 2, 2005

Logged In: YES
user_id=33168

I fixed this problem in 2.5. I am leaving it up to Anthony
whether to backport this to 2.4 or not.

Checked in as:
Misc/NEWS: 1.1383, 1.1193.2.117
Python/pythonrun.c: 2.217, 2.211.2.3
Lib/test/bad_coding.py: 1.1
Lib/test/test_coding.py: 1.1
Parser/parsetok.c: 2.37
Parser/pgenmain.c: 2.32
Parser/tokenizer.c: 2.79

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs)
Projects
None yet
Development

No branches or pull requests

0 participants