Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pygobject pygobject
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 303
    • Issues 303
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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
  • GNOMEGNOME
  • pygobjectpygobject
  • Issues
  • #23
Closed
Open
Issue created Feb 06, 2012 by Bugzilla@bugzilla-migration💬Reporter

Array argument to Python signal callbacks cause crash

Submitted by Paolo Borelli

Link to original bug (#669496)

Description

I saw the following g-i commit:

http://git.gnome.org/browse/gobject-introspection/commit/?id=6757460e4a95f818d3a73d7904ef8a7afb6987fc

I do not think pygobject handles it. Attached there is a very quick unit test which indeed does not pass (though it may also the unit test being buggy, it was a 3 minutes hack just to check if array callbacks were already working)

Depends on

  • Bug 727004
  • Bug 726999
Assignee
Assign to
Time tracking