Re: can't type letter "c" in console

[anatoly techtonik]

On Tuesday, July 24, 2012 7:45:22 AM UTC+3, luke wrote:

I cannot enter the letter "c" into the console. Keyboard works fine and I can use this letter in the editor. What's going on here?

Try --reset option. If it won't help, the problem probably with your system (sticky alt/ctrl/whatever?)

[luke]

Hmm, that did not help. But I don't see how it could be a problem with my system if I can use the letter under all other circumstances (with the various modifiers like ctrl,alt, etc), excluding the console of Spyder. Oh well.

[anatoly techtonik]

Ok. Now you need to find out your version of Spyder, Qt, bindings and
operating system. Telepaths are on vacations, sorry.

> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/spyderlib/-/-FdmvSclOUkJ.
>
> To post to this group, send email to spyd...@googlegroups.com.
> To unsubscribe from this group, send email to
> spyderlib+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/spyderlib?hl=en.

[luke]

Spyder version: py27-spyder-2.1.10_4

Qt stuff:py27-pyqt4-4.9.1_0, qt4-mac-4.8.2_0+quartz

Rope: py27-rope-0.9.2_0

Bindings?

Mac OS X 10.6.8

[anatoly techtonik]

pyqt4 are Python bindings for qt4.

Mac OS X is a pain, because not many contributors who can read and
troubleshoot Python code possess this platform to debug Spyder. But
there is still some hope. Could you "run Spyder from source" or test
if it is repeatable with development snapshot?
http://code.google.com/p/spyderlib/wiki/NoteForBetaTesters

> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/spyderlib/-/hOy6ioidZYEJ.

[luke]

Running from source seems OK.

I've tried deleting and reinstalling all the dependencies for Spyder via MacPorts. The "c" problem persists. So weird.

On Tuesday, July 24, 2012 12:08:59 PM UTC-7, anatoly techtonik wrote:

pyqt4 are Python bindings for qt4.

Mac OS X is a pain, because not many contributors who can read and
troubleshoot Python code possess this platform to debug Spyder. But
there is still some hope. Could you "run Spyder from source" or test
if it is repeatable with development snapshot?
http://code.google.com/p/spyderlib/wiki/NoteForBetaTesters

On Tue, Jul 24, 2012 at 8:41 PM, luke <luke.w...@gmail.com> wrote:
> Spyder version: py27-spyder-2.1.10_4
>
> Qt stuff:py27-pyqt4-4.9.1_0, qt4-mac-4.8.2_0+quartz
>
> Rope: py27-rope-0.9.2_0
>
> Bindings?
>
> Mac OS X 10.6.8
>
> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/spyderlib/-/hOy6ioidZYEJ.
> To post to this group, send email to spyd...@googlegroups.com.
> To unsubscribe from this group, send email to

> spyderlib+unsubscribe@googlegroups.com.

[anatoly techtonik]

You can try to update source to a tag that corresponds to your Spyder
version with:

hg up -r v2.1.10

To me it looks like the problem is on a level above - in Mac version
of Qt or PyQt4 bindings. It may be possible to track other
dependencies for those packages and see if 'c' key works there.

>> > spyderlib+...@googlegroups.com.

>> > For more options, visit this group at
>> > http://groups.google.com/group/spyderlib?hl=en.
>

> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/spyderlib/-/fhg_LrwN6GwJ.

> To post to this group, send email to spyd...@googlegroups.com.
> To unsubscribe from this group, send email to

> spyderlib+...@googlegroups.com.

[anatoly techtonik]

I don't know who maintains the port, but you should contact this
person, definitely.

On Tue, Jul 24, 2012 at 7:40 PM, luke <luke.w...@gmail.com> wrote:
> Well, the standalone version of Spyder for Mac OS does not present the same
> problem. It only seems to exist in the Spyder installed via MacPorts.

>
> On Monday, July 23, 2012 9:45:22 PM UTC-7, luke wrote:
>>
>> I cannot enter the letter "c" into the console. Keyboard works fine and I
>> can use this letter in the editor. What's going on here?
>

> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/spyderlib/-/_ROxXbUr-4UJ.

[luke]

spyder port or the qt port?

[dcn]

I am seeing the same problem.  My setup is messy - I had an old install of Spyder on Lion which I upgraded to Mountain Lion.  I installed the Enthought 7.3.1 distro and then installed Spyder under it using setup.py install.  Running Spyder from the Enthought python command works fine, and the letter "c" works.  However.... I had an old applescript that used to call spyder directly from the Dock, which is still there, and when I ran that, it ran Spyder using the latest Apple Mountain Lion python.  And this one *does* have the "c" problem in the console window.

So the problem may depend on which version of python is being used (and the consequent compiler it used - GCC4.0.1 in Enthought, GCC4.2.1 in the Mountain Lion Apple python).  I will explore further.

DN

[Eric Borisch]

On Monday, August 6, 2012 11:35:48 PM UTC-5, huhwhat wrote:

Just popping in to say that I'm having the exact same problem after upgrading to Mountain Lion. I've tried uninstalling all ports and macports itself, but the problem persists.

Please do a 'sudo port selfupdate' and then 'sudo port upgrade py27-spyder' (or py26-) to make sure you have 'py27-spyder @2.1.11_2' returned when you type 'port echo active and py27-spyder'

This should be fixed now.

Thanks,

 Eric

[David Nicholls]

I've just finished installing py-spyder onto a clean install of Macports. I didn't trust the legacy Macports install from before I upgraded to Mountain Lion, and as Spyder is my current main reason for Macports, I thought I'd give it a fresh start. Initial tests suggest that it works properly.

However, I did strike one problem, which caused libunwind-headers to abort installing. The message in the log file (now erased by a successful install) said I had not agreed to the Xcode license. I had to run:

sudo xcodebuild -license

and enter 'agree' to accept the license,

then clean lib-unwind-headers, before I could continue the installation.

(BTW, the 'c' key now works :-)

DN

> --
> You received this message because you are subscribed to the Google Groups "spyder" group.

> To view this discussion on the web visit https://groups.google.com/d/msg/spyderlib/-/F7PyIiD55zoJ.