Skip to content

Difference in behaviour with grp.getgrgid and pwd.getpwuid #70317

Closed

Description

@SimonFr
mannequin
BPO 26129
Nosy @brettcannon, @larryhastings, @serhiy-storchaka
Files
  • grp_getgrgid_non_integer_gid.patch
  • 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/serhiy-storchaka'
    closed_at = <Date 2016-01-18.16:53:45.421>
    created_at = <Date 2016-01-15.19:48:25.318>
    labels = ['type-bug', 'library']
    title = 'Difference in behaviour with grp.getgrgid and pwd.getpwuid'
    updated_at = <Date 2016-01-18.16:53:45.420>
    user = 'https://bugs.python.org/SimonFr'

    bugs.python.org fields:

    activity = <Date 2016-01-18.16:53:45.420>
    actor = 'serhiy.storchaka'
    assignee = 'serhiy.storchaka'
    closed = True
    closed_date = <Date 2016-01-18.16:53:45.421>
    closer = 'serhiy.storchaka'
    components = ['Library (Lib)']
    creation = <Date 2016-01-15.19:48:25.318>
    creator = 'SimonFr'
    dependencies = []
    files = ['41640']
    hgrepos = []
    issue_num = 26129
    keywords = ['patch']
    message_count = 7.0
    messages = ['258325', '258467', '258468', '258472', '258476', '258525', '258526']
    nosy_count = 6.0
    nosy_names = ['brett.cannon', 'larry', 'SilentGhost', 'python-dev', 'serhiy.storchaka', 'SimonFr']
    pr_nums = []
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue26129'
    versions = ['Python 3.6']

    Activity

    1. SimonFr commented on Jan 15, 2016

      SimonFrmannequin
      MannequinAuthor

      grp.getgrgid is capable of accepting a string:

      from grp import getgrgid
      print(getgrgid('0'))

      However, pwd.getpwuid can't do the same:

      from pwd import getpwuid
      print(getpwuid('0'))
      Traceback (most recent call last):
        File "getpwuid_test.py", line 2, in <module>
          print(getpwuid('0'))
      TypeError: an integer is required

      This seems to be because inside Modules/pwdmodule.c, getpwuid uses PyNumber_ParseTuple with a converter that uses PyNumber_Index to get a Python integer, and that raises an exception on failure.

      However, in Modules/grpmodule.c, grp_getgrgid uses PyNumber_Long (Or PyNumber_Int for an old enough Python) as a conversion first, and as the documentation says at https://docs.python.org/3/c-api/number.html, this is the equivalent of running int(o), which can convert a string to an integer. Only then is it given to PyNumber_Index, by way of a helper function _Py_Gid_Converter

      Should these have different behaviours? Is there a reason for the difference?

      The behaviour of getgrgid seems more helpful, and it's odd that it doesn't apply to both functions. Is this undesirable behaviour in getgrgid or getpwuid?

    2. added
      stdlibStandard Library Python modules in the Lib/ directory
      type-bugAn unexpected behavior, bug, or error
      on Jan 15, 2016
    3. SilentGhost commented on Jan 17, 2016

      SilentGhostmannequin
      Mannequin

      I'm adding Larry since it was his implementation of _Py_Uid_Converter in bpo-15301 that seems to lead to this behaviour.

    4. larryhastings commented on Jan 17, 2016

      @larryhastings
      Contributor

      Nope. Argument Clinic was merged in 3.4, and in 3.3 pwd.getpwuid wouldn't accept strings. So this isn't a bug introduced in the Clinic conversion in 3.4, this is historical behavior, and we can't change it now.

      If anything, I'd prefer that grp.getgrid *didn't* accept strings, but it's too late to change that too. "Helpfully" automatically calling int() on an argument is un-pythonic.

      (To answer your specific questions: they probably shouldn't have different behaviors, and I assume there's no particular reason for the difference. It's probably that they had different implementors, and one did a sloppier job than the other.)

    5. serhiy-storchaka commented on Jan 17, 2016

      @serhiy-storchaka
      Member

      This looks as unintentional consequences of ab0221811771.

      I think the current behavior of grp.getgrgid() is not correct, because it accepts str, float and other types. Python is strong-typed language and shouldn't make unwanted implicit type conversions. I guess the purpose was to support long arguments in Python 2.

      There is similar problem with grp.getgrnam() in 2.7. It accepts arguments of any types and convert them to str by calling str(). I guess the purpose was to support unicode arguments. In 3.x only str is accepted.

      Proposed patch deprecates accepting non-integer arguments in grp.getgrgid(). May be we can just remove this without starting deprecating process. I don't know.

    6. brettcannon commented on Jan 17, 2016

      @brettcannon
      Member

      A single deprecation cycle should be enough since it obviously shouldn't work with floats and strings might make sense but updating code to not use them is easy enough.

    7. python-dev commented on Jan 18, 2016

      python-devmannequin
      Mannequin

      New changeset 65e0e06b70b6 by Serhiy Storchaka in branch 'default':
      Issue bpo-26129: Deprecated accepting non-integers in grp.getgrgid().
      https://hg.python.org/cpython/rev/65e0e06b70b6

    8. serhiy-storchaka commented on Jan 18, 2016

      @serhiy-storchaka
      Member

      Thank you for your review Brett.

    9. transferred this issue fromon Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Labels

    stdlibStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions