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

Better error for "1 in unicodestring" #32465

Closed
akuchling opened this issue Jun 27, 2000 · 5 comments
Closed

Better error for "1 in unicodestring" #32465

akuchling opened this issue Jun 27, 2000 · 5 comments
Assignees

Comments

@akuchling
Copy link
Member

BPO 400646
Nosy @malemburg, @gvanrossum, @akuchling
Files
  • None: None
  • 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 = 'https://github.com/malemburg'
    closed_at = <Date 2000-06-28.14:14:29.000>
    created_at = <Date 2000-06-27.14:37:49.000>
    labels = []
    title = 'Better error for "1 in unicodestring"'
    updated_at = <Date 2000-06-28.14:14:29.000>
    user = 'https://github.com/akuchling'

    bugs.python.org fields:

    activity = <Date 2000-06-28.14:14:29.000>
    actor = 'akuchling'
    assignee = 'lemburg'
    closed = True
    closed_date = None
    closer = None
    components = ['None']
    creation = <Date 2000-06-27.14:37:49.000>
    creator = 'akuchling'
    dependencies = []
    files = ['2471']
    hgrepos = []
    issue_num = 400646
    keywords = ['patch']
    message_count = 5.0
    messages = ['32862', '32863', '32864', '32865', '32866']
    nosy_count = 3.0
    nosy_names = ['lemburg', 'gvanrossum', 'akuchling']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'closed'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue400646'
    versions = []

    @akuchling
    Copy link
    Member Author

    No description provided.

    @gvanrossum
    Copy link
    Member

    Isn't the PyErr_Clear() before the PyErr_Set(...) call redundant?

    @akuchling
    Copy link
    Member Author

    Yes, I suppose it is. Removed.

    @malemburg
    Copy link
    Member

    Checked in... now how do I mark this patch as completed ???

    @akuchling
    Copy link
    Member Author

    Marked as closed; MAL, I think you'd have to be granted
    patch admin privileges. When I view the patch page, the
    category/status/assigned-to fields are all select boxes
    that I can change.

    @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
    None yet
    Projects
    None yet
    Development

    No branches or pull requests

    3 participants