{"id":1097,"date":"2013-08-15T02:05:03","date_gmt":"2013-08-15T02:05:03","guid":{"rendered":"http:\/\/blog.filipesaraiva.info\/?p=1097"},"modified":"2013-12-28T17:21:34","modified_gmt":"2013-12-28T17:21:34","slug":"cantor-dynamic-keywords-in-python-backend","status":"publish","type":"post","link":"https:\/\/filipe.saraiva.tec.br\/blog\/?p=1097","title":{"rendered":"Cantor – dynamic keywords in python backend"},"content":{"rendered":"

In previous post<\/a>, I mentioned about dynamic keywords in python backend. The idea is, after import a python module in Cantor workspace, functions, keywords, variables, and more from this module are load by Cantor and available to syntax highlighting and tab complete.<\/p>\n

This feature is implemented for now. You can test it compiling Cantor from python-backend branch<\/a>.<\/p>\n

But, let me show more information about this feature.<\/p>\n

There are several ways to import a python module in python console. You have “import modulename”, “import modulename as modulevariable”, “from modulename import *”, “from modulename import function_1, function_2, …”, and more. Each import way causes different consequences to user experience.<\/p>\n

The four import ways mentioned in previous paragraph are supported by python backend. I will show these different import ways and how python backend behave for each one.<\/p>\n

import modulename<\/strong><\/p>\n

<\/strong>The more basic import way. After this command, a variable named “modulename” is defined and the functions and more keywords of this module are available to access using “modulename.keyword”.<\/p>\n

\"python_import_modulename\"<\/a>Tab Complete<\/em><\/em><\/p>\n

\"python_import_modulename_highlighting\"<\/a><\/p>\n

Syntax Highlighting<\/em><\/p>\n

import modulename as modulevariable<\/strong><\/p>\n

This way the user define a name “modulevariable” to reference “modulename”, and “modulename” is not defined. So, you can access the functions and more from “modulename” using “modulevariable.keyword”.<\/p>\n

\"python_import_modulename_as_modulevariable\"<\/a><\/p>\n

Tab Complete<\/em><\/p>\n

\"python_import_modulename_as_modulevariable_highlithing\"<\/a><\/p>\n

Syntax Highlighting<\/em><\/p>\n

from modulename import *<\/strong><\/p>\n

This way the user import all functions and keywords from “modulename” but anything variable is defined to access “modulename”. The functions of the module are accessed directly.<\/p>\n

\"python_from_modulename_import_all\"<\/a><\/p>\n

Tab Complete<\/em><\/p>\n

\"python_from_modulename_import_all_highlithing\"<\/a><\/p>\n

Syntax Highlighting<\/em><\/p>\n

from modulename import function_1, function_2, …<\/strong><\/p>\n

The user import only specific functions from a “modulename”, no all functions.<\/p>\n

\"python_from_modulename_import_specific\"<\/a><\/p>\n

Tab Complete<\/em><\/p>\n

\"python_from_modulename_import_specific_highlithing\"<\/a><\/em><\/p>\n

Syntax Highlighting<\/em><\/p>\n

Cantor plugin<\/strong><\/p>\n

I developed a Cantor plugin to import modules. This plugin open a dialog to user enter a modulename and, after press Ok, Cantor run “import modulename” and keywords are available. The diaglog is accessible by “Packaging” menu, in toolbar.<\/p>\n

\"python_import_cantor_plugin\"<\/a><\/em><\/p>\n

Cantor Plugin<\/em><\/p>\n

Handling Errors<\/strong><\/p>\n

The backend can identify several errors during import.<\/p>\n

\"python_import_errors\"<\/a><\/p>\n

Handling Errors<\/em><\/p>\n

Conclusions<\/strong><\/p>\n

Well, the feature is working and it is mature for use, however it don’t support all import ways in python. But, I think these five ways cover the most commons import ways used by most python scientific users.<\/p>\n

The important thing is, this feature enable python backend to support the several python modules, and no only scipy, numpy, and matplotlib, as I proposed<\/a> in begin of this project.<\/p>\n

Let me know how you import a module in python. I will develop support to more import ways in future versions of the backend.<\/p>\n

For now, wait for more news of this project soon!<\/p>\n","protected":false},"excerpt":{"rendered":"

In previous post, I mentioned about dynamic keywords in python backend. The idea is, after import a python module in Cantor workspace, functions, keywords, variables, and more from this module are load by Cantor and available to syntax highlighting and tab complete. This feature is implemented for now. You can test it compiling Cantor from… Continue a ler »Cantor – dynamic keywords in python backend<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[9],"tags":[58,48,11,47,101,26,51,109,104,41,52,108,80],"class_list":["post-1097","post","type-post","status-publish","format-standard","hentry","category-software-livre","tag-cantor","tag-comunidade","tag-desenvolvimento","tag-gsoc","tag-gsoc2013-python-backend","tag-kde","tag-planet-mageia-english","tag-planet-python","tag-planet-scipy","tag-planeta-psl-pi","tag-planetkde-english","tag-python","tag-python-backend"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1p2Jh-hH","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"_links":{"self":[{"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1097","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1097"}],"version-history":[{"count":2,"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1097\/revisions"}],"predecessor-version":[{"id":1109,"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1097\/revisions\/1109"}],"wp:attachment":[{"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1097"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1097"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/filipe.saraiva.tec.br\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1097"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}