[et_pb_section fb_built=”1″ _builder_version=”4.27.4″ background_color=”#009EBD” custom_margin=”0px||0px||true” custom_padding=”33px||33px||true|” hover_enabled=”0″ global_colors_info=”{}” background_enable_image=”off” sticky_enabled=”0″][et_pb_row _builder_version=”4.16″ custom_margin=”0px||0px||true|false” custom_padding=”40px||40px||true|false” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_post_title featured_image=”off” text_color=”light” _builder_version=”4.27.4″ text_orientation=”center” hover_enabled=”0″ global_colors_info=”{}” meta=”off” sticky_enabled=”0″][\/et_pb_post_title][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”][et_pb_row _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”60px||0px||false|false” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”]<\/p>\n
Here we are at a long awaited moment within our team: The passage of WAPT to version 2.0<\/strong>! As you can see, the development of this version pushes us to a new level!<\/strong> Let’s discover together what this version contains!<\/p>\n Before we go any further and to simplify your reading, we have to go back to one of our previous announcements. If you are not aware of the end of WAPT Community<\/a>, please refer to our dedicated blog post. We’ll meet you here, right after!<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”][et_pb_row _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”50px||0px||false|false” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”]<\/p>\n The development of this version is a bit special. The end of Python 2.7 support<\/strong> has guided our roadmap. This rewriting work has therefore required a lot of time<\/strong>. Nevertheless, we wanted WAPT 2.0 to have new features as well.<\/p>\n So what’s new in WAPT 2.0?<\/p>\n Without forgetting the creation of our brand new free version of WAPT: WAPT Discovery<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”][et_pb_row module_id=”python-3″ _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”50px||0px||false|false” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n As we explained in the introduction, the Python 2.7 language, formerly used in WAPT, is no longer supported. We have therefore decided to integrate the higher version<\/strong> into the core of WAPT. WAPT Enterprise and WAPT Discovery benefit from this change<\/strong>.<\/p>\n Security has always been at the heart of WAPT development, especially since the ANSSI qualification<\/a>. This is also the case for this version 2.0 ! Thus, for obvious security reasons<\/strong>, we could not (and did not want to) keep an unsupported language<\/strong>.<\/p>\n Moreover, the switch to Python 3 allows us to support new libraries<\/strong>. An interesting advantage, especially if you develop your own packages!<\/p>\n Since we are talking about WAPT packages, we have to give you some details about this. The new version of Python<\/a> relies on new encryption libraries, so it will be necessary to resign all your packages<\/strong>. It is also possible that some of your packages are not compatible with the Python 3 syntax<\/strong>, so you will have to correct these packages to make them compatible<\/strong> with Python 3 and then redeploy them on your computer<\/strong>.<\/p>\nWhat’s new in WAPT 2.0?<\/span><\/h2>\n
\n
WAPT uses Python 3<\/span><\/h2>\n
Why is WAPT based on Python 3?<\/h3>\n
WAPT changes related to the switch to Python 3:<\/h3>\n