Does "SyntaxEditor Python Language Add-on for WPF" support Python 3.6

SyntaxEditor Python Language Add-on for WPF Forum

Posted 1 year ago by Jamie L. Palmer
Version: 16.1.0675
Avatar

We are in the process of updating our code to use Python 3.6.  Since we are using the "SyntaxEditor Python Language Add-on for WPF" provided by you, I was wondering if you knew if switching our code to use "ActiproSoftware.Text.Languages.Python.PythonVersion.Version3" when creating "PythonSyntaxLanguage" would already work just fine with Python 3.6?  

We are currently using your application versioned 2016.1 if that makes a difference to your answer.

Comments (6)

Posted 1 year ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Jamie,

I believe the add-on is currently on v3.4.1.  We have a TODO item to update the version support and will log your request with it.  At the moment, we're working on wrapping up the first beta for the WPF SyntaxEditor 2019.1 release, which is described as "SyntaxEditor vNext" in our blog.


Actipro Software Support

Posted 8 months ago by Christine Gillin
Avatar

Hi-

Its been a while, is there an update to this answer? I am using v19.1.682 right now.

Thanks!

Posted 8 months ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Christine,

Not yet, we have been letting the SyntaxEditor updates settle a bit now that all the platforms (WPF, WinForms, UWP) are on the same codebase and shifted gears to working on enhancements to our WPF Themes.  Themes is our current focus for the first 2020.1 version.  After that, updating the SyntaxEditor add-ons are high priority items.


Actipro Software Support

The latest build of this product (v2019.1 build 0686) was released 1 month ago, which was before the next post in this thread.
Posted 14 days ago by Ravi Prabakaran
Avatar

Hi,

Any update to this answer?

Thanks!

[Modified 14 days ago]

Posted 14 days ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Ravi,

Not yet, we are very close to finally having the 2020.1 version out.  That has taken a lot longer than we anticipated (but the updates will be well worth it) so everything on the TODO list has gotten pushed back accordingly.


Actipro Software Support

Posted 6 days ago by Jamie L. Palmer
Avatar

This may or may not be useful to you, but I wanted to put it on your radar in case it is helpful. 

When figuring out the new functionality in Python 3.6-3.8 that my project is either going to use or wants to use; we attempted to identify those that may cause syntax changes and thus may not be handled well in the current SyntaxEditor that we are using (v19.1.682) until we get the updated version to handle Python 3.6.  There may be other syntax changes in the various updates to Python, but I know these are ones that we are hoping to utilize. 

Good luck!

The following is the list we came up with:

==========
Python 3.6
==========

New syntax features we use:
===========================
PEP 498, formatted string literals.  https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-pep498
PEP 515, underscores in numeric literals.  https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-pep515
PEP 526, syntax for variable annotations.  https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-pep526

Syntax we might use:
====================
PEP 525, asynchronous generators.  https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-pep525
PEP 530: asynchronous comprehensions.  https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-pep530


==========
Python 3.7
==========

Syntax we might use:
====================
async and await are now reserved keywords.


==========
Python 3.8
==========

New syntax features we will use:
================================
Assignment Expressions (walrus operator) https://www.python.org/dev/peps/pep-0572/
Positional Only Parameters https://www.python.org/dev/peps/pep-0570/
f-strings support = for self-documenting expressions and debugging  https://docs.python.org/3/whatsnew/3.8.html#f-strings-support-for-self-documenting-expressions-and-debugging

Add Comment

Please log in to a validated account to post comments.