[MonoDevelop] Python Support for MonoDevelop on OS X

[Michael Hutchinson]

On Sun, May 24, 2009 at 6:56 PM, Michael Foord
<fuzzyman at voidspace.org.uk> wrote:
>
>
> "<unnamed thread>" tid=0x0xb0289000 this=0x0xea5898 thread handle 0x180
> state : interrupted state owns ()
>   at string.op_Equality (string,string) [0x00000] in
> /private/tmp/monobuild/build/BUILD/mono-2.4/mcs/class/corlib/Assembly/AssemblyInfo.cs:1
>   at MonoDevelop.Core.Assemblies.TargetRuntime.FindInstalledAssembly
> (string,string) [0x0009d] in
> /home/michael/mono/monodevelop-working/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Assemblies/TargetRuntime.cs:336
>   at MonoDevelop.Projects.ProjectReference.UpdateGacReference () [0x00013]
> in
> /home/michael/mono/monodevelop-working/main/src/core/MonoDevelop.Projects/MonoDevelop.Projects/ProjectReference.cs:264
>   at MonoDevelop.Projects.ProjectReference.ResetReference () [0x00025] in
> /home/michael/mono/monodevelop-working/main/src/core/MonoDevelop.Projects/MonoDevelop.Projects/ProjectReference.cs:324
>   at MonoDevelop.Projects.DotNetProject.UpdateSystemReferences () [0x000c5]
> in
> /home/michael/mono/monodevelop-working/main/src/core/MonoDevelop.Projects/MonoDevelop.Projects/DotNetProject.cs:708
>   at MonoDevelop.Projects.DotNetProject.set_TargetFramework
> (MonoDevelop.Core.Assemblies.TargetFramework) [0x00062] in
> /home/michael/mono/monodevelop-working/main/src/core/MonoDevelop.Projects/MonoDevelop.Projects/DotNetProject.cs:178
>   at MonoDevelop.Projects.Formats.MSBuild.MSBuildProjectHandler.Load
> (MonoDevelop.Core.IProgressMonitor,MonoDevelop.Projects.Formats.MSBuild.MSBuildProject)
> [0x00104] in
> /home/michael/mono/monodevelop-working/main/src/core/MonoDevelop.Projects/MonoDevelop.Projects.Formats.MSBuild/MSBuildProjectHandler.cs:226

Hm, looks like the reference resolution is stuck. No idea why.

Can you consistently reproduce this? Does it happen with all projects
or just PyBinding?

-- 
Michael Hutchinson
http://mjhutchinson.com