Ticket #1058 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Pippy module not in correct path

Reported by: dr.dolittle Owned by: lfaraone
Priority: High Milestone: 0.88
Component: Sugar on a Stick (SoaS) Version: 0.84.x
Severity: Unspecified Keywords: r?
Cc: mtd Distribution/OS: Unspecified
Bug Status: Needinfo

Description

Trying to run certain scripts in pippy fails immediately due to ImportError: no module named pippy.

Attachments

sugar-1058.patch Download (1.3 KB) - added by alsroot 4 years ago.

Change History

Changed 4 years ago by tomeu

  • owner changed from tomeu to lfaraone
  • component changed from sugar to Pippy

I think this has been fixed?

Changed 4 years ago by tomeu

  • status_field changed from Unconfirmed to Needinfo
  • milestone changed from Unspecified by Release Team to 0.86

Changed 4 years ago by alsroot

  • keywords r? added; pippy Import:Error removed

Changed 4 years ago by mtd

  • cc mtd added

this patch is against git HEAD (version 34) but the version that's on a.sl.o is 35 and appears to be the git "groupthink" git branch

Changed 4 years ago by mtd

sorry - the patch applies fine to the groupthink branch, just with a bit of fuzz. I looked at the wrong self._vte.fork_command invocation in the source code, sorry.

Changed 4 years ago by RafaelOrtiz

  • milestone changed from 0.86 to 0.88

Changed 4 years ago by alsroot

Changed 4 years ago by alsroot

I guess problems was with not passing PYTHONPATH envvar(it some cases it works fine but in other cases doesn't, didn't investigate it dipper), so I just replaced sh invocation with /bin/env and it works in all of my envs.

Changed 4 years ago by dsd

This is a bug in vte's python bindings

 https://bugzilla.gnome.org/show_bug.cgi?id=587894

Already fixed upstream

I vote leave the patch out and fix the bindings.. Fedora here:  https://bugzilla.redhat.com/show_bug.cgi?id=537391

Changed 4 years ago by sascha_silbe

Update request filed at  Debian.

Changed 4 years ago by sascha_silbe

Fixed version (0.22.3 also contains the fix, not just 0.23.1 like I assumed) already in Debian sid, should be in squeeze as well soon.
Ubuntu  seems to have a fixed version as well.

Changed 3 years ago by dsd

  • status changed from new to closed
  • resolution set to fixed

F11 fixed as well, F12 was already working, so I think we can close this bug

Changed 3 years ago by sascha_silbe

  • distribution changed from SoaS to Unspecified
  • component changed from Pippy to SoaS

Bulk change distribution=SoaS -> component=SoaS

Note: See TracTickets for help on using tickets.