pythonika icon indicating copy to clipboard operation
pythonika copied to clipboard

Automatically exported from code.google.com/p/pythonika

Results 7 pythonika issues
Sort by recently updated
recently updated
newest added

``` What steps will reproduce the problem? 1. After pointing to correct homebrew Python 2.7 and added -arch i386 to the Makefile, I can build the object file. 2. But...

Priority-Medium
Type-Defect
auto-migrated

``` Any idea why? ``` Original issue reported on code.google.com by `[email protected]` on 17 Dec 2014 at 4:08

Priority-Medium
Type-Defect
auto-migrated

``` This may be an extremely naive question, but I cannot understand how to download (and subsequently make) the makefile. The only download that I find that is suitable for...

Priority-Medium
Type-Defect
auto-migrated

``` OSX builds require the mathlink Framework to be copied to (or already available in) @executable_path/../Frameworks The documentation should make this clear, or an install build should be defined that...

Priority-Medium
Type-Defect
auto-migrated

``` I've experienced incorrect encoding with non-ascii (namely, cyrillic) str and unicode objects (see http://mathematica.stackexchange.com/questions/25730/string-encoding-issue-with- pythonika/25738). I've fixed it, probably in a hacky way (as I'm not quite good at...

Priority-Medium
Type-Defect
auto-migrated

``` The version of Makefile.linux included with SVN revision 4 fails to compile Pythonika using Mathematica 8 on x86-64. With the following changes to the Makefile (also provided as an...

Priority-Medium
Type-Defect
auto-migrated

``` It appears that Pythonika's symbols, including its private variables (such as "code") are not put in a separate context. If I already have a variable named "code", it will...

Priority-Medium
Type-Defect
auto-migrated