Skip to content
This repository has been archived by the owner on Jan 16, 2025. It is now read-only.

Weechat fails to launch with Python 2.7.4 #19168

Closed
ghost opened this issue Apr 13, 2013 · 10 comments
Closed

Weechat fails to launch with Python 2.7.4 #19168

ghost opened this issue Apr 13, 2013 · 10 comments
Labels

Comments

@ghost
Copy link

ghost commented Apr 13, 2013

Hi, weechat suddently stopped working for me today right after I upgraded to python 2.7.4.

My brew doctor is clean.
OS: OS X 10.8

When I open Weechat, it fails to launch and outputs something like it found an ImportError when importing MAXREPEAT from _sre. I even started weechat with 0 plugins but got the same error message.

However, when I removed the Current Python framework symlink in /System/Library/Frameworks/Python.framework/Current, weechat installs and runs fine with Python 2.7.2, the default python version built by Apple.

Here's what it looks like when I launch Weechat when building it with python 2.7.4:
Weechat error

@allait
Copy link

allait commented Apr 13, 2013

I think this isn't limited to weechat: I get the same error when launching brewed macvim and the system vim (which is linked with python/dyn) after upgrading to python 2.7.4 on OS X 10.8. Homebrew vim works fine however, so I assume it has something to do with how apps link with python. Also, it's possible to build a working version of macvim using the symlink trick from #17908, maybe the same thing would work for weechat.

@ghost
Copy link
Author

ghost commented Apr 13, 2013

Just tried the symlink trick but it didn't work for weechat. I followed all the steps but it still gave me the same errors.

I actually didn't have a problem building Macvim with python. It just worked for me.

@allait
Copy link

allait commented Apr 13, 2013

I should have clarified that: building macvim works, only python integration doesn't. If you have plugins using python, then macvim will fail to start. In any case typing :python '' into macvim and system vim will also produce an error.

@heygarrett
Copy link

Weechat fails to launch for me as well with python 2.7.4 on OS X 10.8.3.
Screen Shot 2013-04-15 at 11 09 07 AM

Edit: I should mention, my terminal then doesn't accept input after throwing this error. I have to close the current and open a new terminal window.

@dmarr
Copy link
Contributor

dmarr commented Apr 16, 2013

Getting this same error when trying to launch vim/macvim after a rebuild.

@marksutherland
Copy link

I can run weechat-curses, but attempting to load python fails:

/plugin load python
23:07:04 weechat =!= | Error: unable to load plugin "python": dlopen(python, 10): image not found
23:07:04 weechat =!= | If you're trying to load a script and not a C plugin, try command to load scripts (/perl, /python, ...)

I recently reinstalled python, and reinstalling weechat didn't seem to make a difference either.

@heygarrett
Copy link

@marksutherland You have to compile with flags for those plugins. Check brew options weechat for the flags to compile weechat with python, ruby, perl, etc.

@marksutherland
Copy link

Ah! Awesome, never mind then :)

@durka
Copy link
Contributor

durka commented May 2, 2013

#19300

@ghost ghost assigned samueljohn May 3, 2013
@samueljohn
Copy link
Contributor

I could reproduce this and have a fix in the pipeline which I hope to push this weekend (it's included in #18588).

However, this issue here is a dupe of #19300. Therefore closing this now.
I'll take a look at macvim, too, it's probably fixed by then.

adamv pushed a commit that referenced this issue May 24, 2013
* fixes CMake Python detection

Fixes #19168.
Closes #20025.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
handyman5 pushed a commit to handyman5/homebrew that referenced this issue Oct 7, 2013
* fixes CMake Python detection

Fixes Homebrew#19168.
Closes Homebrew#20025.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
@gpakosz gpakosz mentioned this issue Feb 9, 2014
@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants