I would like to use my Canopy editor with "easygui", but I can't install it from the package Manager.
Is there any way I could do it from shell without damaging anything?
Thanks a lot in advance!
edit
simplest program:
import easygui
path = easygui.fileopenbox()
I get a big report and no execution...
For example:
0 CoreFoundation 0x92e88471 __raiseError + 193
1 libobjc.A.dylib 0x9b7c4091 objc_exception_throw + 162
2 CoreFoundation 0x92e8ccb3 -[NSObject(NSObject) doesNotRecognizeSelector:] + 275
...
84 Python 0x00011110 PyObject_CallObject + 32
85 libpyside-python2.7.1.2.2.dylib 0x0054ca19
_ZN6PySide13SignalManager20callPythonMetaMethodERK11QMetaMethodPPvP7_objectb + 121
No problem, no harm, to install it following https://support.enthought.com/entries/23389761-Installing-packages-into-Canopy-Python-from-the-command-line
I have no information about how well it will work. You can use it from a Canopy Command Prompt (Windows) or Terminal (OSX/Linux). If you use it from inside the Canopy GUI, be sure to change the Pylab backend (in Preferences/Python) to Inline (SVG) as it will conflict with the Interactive backends.
Related
Ever since Xcode 11 I've not been able to run any apps on my device. They will launch in the simulator just fine. I have an iPhone 11 Max Pro.
I've tried everything I can think of to get it to work and I have no idea what to do at this point. Has anyone figured out a fix ?
I did try setting my project to Legacy build and I still have the same issue.
Here are the details of the failed install to my iPhone.
Details
Unable to install "App Test"
Domain: com.apple.dtdevicekit
Code: -402620395
--
App installation failed
Domain: com.apple.dtdevicekit
Code: -402620395
Failure Reason: A valid provisioning profile for this executable was not found.
User Info: {
DVTRadarComponentKey = 487927;
"com.apple.dtdevicekit.stacktrace" = (
0 DTDeviceKitBase 0x00000001251586e7 DTDKCreateNSError + 109
1 DTDeviceKitBase 0x0000000125158de9 DTDK_AMDErrorToNSError + 792
2 DTDeviceKitBase 0x000000012519856a __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 164
3 DVTFoundation 0x000000010b27cc22 DVTInvokeWithStrongOwnership + 73
4 DTDeviceKitBase 0x0000000125198301 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1589
5 IDEiOSSupportCore 0x0000000125020a25 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.352 + 4523
6 DVTFoundation 0x000000010b3ade8a __DVT_CALLING_CLIENT_BLOCK__ + 7
7 DVTFoundation 0x000000010b3af562 __DVTDispatchAsync_block_invoke + 809
8 libdispatch.dylib 0x00007fff6d6ca583 _dispatch_call_block_and_release + 12
9 libdispatch.dylib 0x00007fff6d6cb50e _dispatch_client_callout + 8
10 libdispatch.dylib 0x00007fff6d6d0ace _dispatch_lane_serial_drain + 597
11 libdispatch.dylib 0x00007fff6d6d1452 _dispatch_lane_invoke + 363
12 libdispatch.dylib 0x00007fff6d6daa9e _dispatch_workloop_worker_thread + 598
13 libsystem_pthread.dylib 0x00007fff6d9256fc _pthread_wqthread + 290
14 libsystem_pthread.dylib 0x00007fff6d924827 start_wqthread + 15
);
}
--
I faced this issue today and I could not fix it either with the proposed solutions that are out there, because they pointed into the wrong direction.
Do you, by any chance, have frameworks included in your project and set them to "embed without signing"? Changing the included frameworks to "embed & sign" fixed this issue for me.
Not properly re-signing external frameworks seems to cause problems when attempting to install the binary to a real device. The executable mentioned in "A valid provisioning profile for this executable was not found." does in this context refer to the insufficiently signed external framework.
I upgraded to XCode 8, and I am going through hell of being able to run my tests sometimes... For example, I just was testing some code, and was able to run my tests 3 times in a row... and then the 4th time I got:
dyld: could not load inserted library 'PLATFORMS/iPhoneOS.platform/Developer/Library/PrivateFrameworks/IDEBundleInjection.framework/IDEBundleInjection' because image not found
*** If you believe this error represents a bug, please attach the log file at /Users/patrick/Library/Developer/Xcode/DerivedData/MyApp-hjfppqmgxqrprucknvwtakynpqxs/Logs/Test/2B6C2EAE-5C13-40C9-BACE-3A00AA74F3EF/Session-UnitTests-2016-09-20_124123-gk3pW0.log
I have rebooted my iOS device, rebooted my computer, deleted derrived data, etc... It will no longer run tests. ARRRGH!!!!
UPDATE
I should mention, I am trying to run tests on my iPad, I can't run tests on the simulator because I have too much code having to do with NEON intrinsics, and so the simulator wont run.
But what does seem to work is, when this happens, switch to build tests on my iPhone, then it when it builds, it just says "running tests" and the spinner spins forever, but no tests are actually running... I can actually tap on my app and interact with it, which is usually not the behavior I get when running tests... Anyway I then stopped the build, switched back to my iPad and now tests run again.
I get this error consistently with XCode 8.0 running on my iPad (Version 10.0.2 (14A456)) when I run test code that causes an uncaught exception in the code under test. There may be other examples, but it happens any time the code under test fails catastrophically.
When the unit test fails with an exception, XCode does not recover properly.
I believe this is a problem with XCode; this answer provides a workaround. The unit test will fail at the exception, and subsequent runs produce the 'image not found' error.
The simplest recovery I've found is the following:
Set device target to Generic iOS Device
Disconnect my iPad
Reboot the iPad
Connect everything back together
Here is an example failure that demonstrates the problem;
Notice that the core issue in this example is that I have written a bad unit test; I'm passing a nil parameter to a method that is subsequently used to try adding a nil object to a dictionary.
Update: for the sake of accuracy, the issue was that I was passing an immutable dictionary as a parameter when a mutable one was expected, thus producing the 'unrecognized selector' error. In any case, the exception is what causes XCode to behave badly.
Assertions: failed: caught "NSInvalidArgumentException", "-[__NSDictionaryI setObject:forKey:]: unrecognized selector sent to instance 0x1818f200"
(
0 CoreFoundation 0x1dd89e1f <redacted> + 154
1 libobjc.A.dylib 0x1cfef077 objc_exception_throw + 38
2 CoreFoundation 0x1dd8f515 <redacted> + 0
3 CoreFoundation 0x1dd8d589 <redacted> + 700
4 CoreFoundation 0x1dcb2f08 _CF_forwarding_prep_0 + 24
5 tDefense 0x000cd299 +[PlayingPiece addPlayingPiece:atLocation:onBoard:] + 326
6 tDefense 0x000cd5ad +[PlayingPiece addNewPiece:atLocation:onBoard:] + 154
7 tDefenseTests 0x00410777 -[PlayFieldTests testGetNeighbors] + 4594
8 CoreFoundation 0x1dd8e864 <redacted> + 68
9 CoreFoundation 0x1dcaf349 <redacted> + 294
10 XCTest 0x00307de5 __24-[XCTestCase invokeTest]_block_invoke_2 + 472
11 XCTest 0x0033b0dd -[XCTestContext performInScope:] + 312
12 XCTest 0x00307c07 -[XCTestCase invokeTest] + 296
13 XCTest 0x00308439 -[XCTestCase performTest:] + 560
14 XCTest 0x0030578d -[XCTestSuite performTest:] + 520
15 XCTest 0x0030578d -[XCTestSuite performTest:] + 520
16 XCTest 0x0030578d -[XCTestSuite performTest:] + 520
17 XCTest 0x002f1d55 __25-[XCTestDriver _runSuite]_block_invoke + 52
18 XCTest 0x00312325 -[XCTestObservationCenter _observeTestExecutionForBlock:] + 628
19 XCTest 0x002f1bed -[XCTestDriver _runSuite] + 512
20 XCTest 0x002f29b7 -[XCTestDriver _checkForTestManager] + 300
21 XCTest 0x0033c55b _XCTestMain + 690
22 CoreFoundation 0x1dd45bc3 <redacted> + 10
23 CoreFoundation 0x1dd455a7 <redacted> + 230
24 CoreFoundation 0x1dd43a61 <redacted> + 752
25 CoreFoundation 0x1dc93073 CFRunLoopRunSpecific + 486
26 CoreFoundation 0x1dc92e81 CFRunLoopRunInMode + 104
27 GraphicsServices 0x1f43bbfd GSEventRunModal + 156
28 UIKit 0x22e34acf <redacted> + 574
29 UIKit 0x22e2f201 UIApplicationMain + 150
30 tDefense 0x000d690f main + 106
31 libdyld.dylib 0x1d45e50b <redacted> + 2
)
File: <unknown>
I was having exactly the same problem after upgrading to Xcode 8 / Swift 2.3. One of deleting derived data, rebooting the phone and closing and re-opening Xcode just fixed it.
I am trying to build NPAPI plugin for safari and have been trying to run the simple NPAPI plugin example from https://github.com/mikma/npsimple on Safari on Mac.
The plugin can use npapi library from WEBKIT_DARWIN_SDK or from XULRUNNER_SDK (downloaded from mozilla.org for mac os).
The plugin works as expected by using WEBKIT_DARWIN_SDK but since it conflicts with my other libraries I can't use it. Now the only way left is to use XULRUNNER_SDK but using that results in a crash on NP_Initialize. Since this is the most basic application using NPAPI it is expected to work ( everything is same expect the fact that internal implementation of webkit and xulrunner could be different).
Am I missing something here?
Pasting initial few lines from the log
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 net.webvm 0x00000001004f8228 NP_GetEntryPoints + 24
1 net.webvm 0x00000001004f82b3 NP_Initialize + 67
2 com.apple.WebKit.PluginHost 0x00000001cfb65188 0x1cfb52000 + 78216
3 com.apple.WebKit.PluginHost 0x00000001cfb599e1 0x1cfb52000 + 31201
4 com.apple.WebKit.PluginHost 0x00000001cfb54ad3 0x1cfb52000 + 10963
5 com.apple.CoreFoundation 0x00007fff84fe9a49 __CFRunLoopDoBlocks + 297
6 com.apple.CoreFoundation 0x00007fff84fabe76 __CFRunLoopRun +
You might want to try starting from the npapi-sdk Mac example, which is both simpler than npsimple and more up to date.
Should I be able to set breakpoints inside the Cocoa framework itself?
I've been seeing various crashes in my Mac OS X application, sometimes randomly. Here's part of an example call stack from Xcode:
0 - 0x98ed0e20 in __CFRunLoopRun
1 - 0x98ece464 in CFRunLoopRunSpecific
2 - 0x98ece291 in CFRunLoopRunInMode
3 - 0x96a90004 in RunCurrentEventLoopInMode
4 - 0x96a8fdbb in ReceiveNextEventCommon
5 - 0x96a8fc40 in BlockUntilNextEventMatchingListInMode
6 - 0x925b078d in _DPSNextEvent
7 - 0x925affce in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
8 - 0x92572247 in -[NSApplication run]
9 - 0x021f009c in QEventDispatcherMac::processEvents at qeventdispatcher_mac.mm:591
10 - 0x01e47742 in QEventLoop::processEvents at qeventloop.cpp:149
11 - 0x01e4799e in QEventLoop::exec at qeventloop.cpp:201
12 - 0x01e49a33 in QCoreApplication::exec at qcoreapplication.cpp:1003
13 - 0x02254c54 in QApplication::exec at qapplication.cpp:3581
When I click on lines 0 - 8, Xcode displays disassembly.
I've changed my Xcode project so that it uses the _debug suffix when loading frameworks. This allows me to step through the Qt code in lines 9 - 13, but line 8 is called at startup and crashes can happen at any time after that.
If I can't set breakpoints, are there any tools that might help me debug problems like this?
Thanks in advance.
You can set up a breakpoint so it breaks on code outside your own. But you will not be able to see the source because you don't have the source code.
In xCode (3.x.x)
"Run->Manage Breakpoints->Add Symbolic Breakpoint"
In XCode 4 you can create a symbolic breakpoint with
Product->Debug->Create Symbolic Breakpoint...
In XCode 5
Debug->Breakpoints->Create Symbolic Breakpoint
I just bought a new Mac and am running Mac OS X 10.6.4 and trying to run Interface Builder 3.2.4 and when I do it consistently crashes with the following error message:
Assertion Message: Unimplemented error handling: You don’t have permission to save the file “Library” in the folder “Interface Builder 3.0”.
Thread 0 Asserted:
0 InterfaceBuilderKit 0x000000010011d74b -[IBLibraryController libraryStoragePath] + 419
1 InterfaceBuilderKit 0x000000010011d40c -[IBLibraryController userObjectsStoragePath] + 33
2 InterfaceBuilderKit 0x000000010011c8e8 -[IBLibraryController loadUserAssets] + 41
3 InterfaceBuilderKit 0x000000010011c83d -[IBLibraryController restoreUserPreferences] + 27
4 Interface Builder 0x0000000100002396
5 AppKit 0x00007fff8000d798 -[NSApplication run] + 80
6 AppKit 0x00007fff800065f8 NSApplicationMain + 364
7 Interface Builder 0x0000000100001c44
8 Interface Builder 0x0000000000000002
Does anyone have any thoughts on this? It seems like it would be easy enough to try and modify the permissions of a folder, but I have no clue where to find the folder “Interface Builder 3.0”.
I feel dumb now, but hopefully this will help someone along the way. I found the "Interface Builder 3.0" folder in ~/Library/Application Support. My user account only had "Read" access so I changed the permissions to "Read & Write".