Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pygobject pygobject
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 281
    • Issues 281
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • pygobjectpygobject
  • Issues
  • #134
Closed
Open
Created Jun 28, 2017 by Bugzilla@bugzilla-migration💬Reporter

Gio.Settings: Cannot handle allowed type range class range

Submitted by Alex Stewart

Link to original bug (#784307)

Description

The __setitem__ binding for gsettings objects apparently doesn't support setting any keys which have range restrictions. This dramatically reduces their usefulness in a lot of situations.

An example I just personally ran into:

>>> Gio.Settings.new('org.gnome.system.proxy.http')['port'] = 8080
Traceback (most recent call last):
  File "`<stdin>`", line 1, in `<module>`
  File "/usr/lib/python3/dist-packages/gi/overrides/Gio.py", line 112, in __setitem__
    raise NotImplementedError('Cannot handle allowed type range class ' + str(type_))
NotImplementedError: Cannot handle allowed type range class range

Poking around a bit, I discovered that Bug 746724 (which is not specifically for this issue but is related) has an offered patch which I believe would solve this problem, if it were merged in, but that ticket appears to have been in the "New" state for over two years now with nobody even looking at it..?

Edited Jan 12, 2018 by Christoph Reiter
Assignee
Assign to
Time tracking