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 279
    • Issues 279
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • pygobjectpygobject
  • Merge requests
  • !3

Merged
Created Jan 15, 2018 by Christoph Reiter@creiter🐍Maintainer

overrides: Fix Gtk.Adjustment.__init__ overrides not setting "value" sometimes. Fixes #151

  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 2

Gtk.Adjustment allows passing positional arguments to init which get translated to a dict for passing to GObject.Object.init. In case of the first argument "value", if "value" is passed before the upper and lower bound to Object.init it will be set to 0 instead.

In Python 2 this happened to work (at least on my machine) because "value" got placed after the bounds (in terms of iteration order) in the final dict value passed to Object.init.

To work around this, set "value" again after init(). A similar work around already exists when "value" is passed as a kwarg.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: gtk-adjustment-init-override-value-bug