Why doesn't "<" work in Code?

[JeffreyYu]

When I run:

turnaround = "Normal (3 day turnaround)"
return turnaround

It returns "Normal" without a problem.

But when I run:

turnaround = "Normal (<3 day turnaround)"
return turnaround

It returns: EOL while scanning string literal (<string>, line 3)

Why does the < character cause this issue? how can i work around it?

 

[ArshilAhmad]

Hi @JeffreyYu,

Could you please record a short video of running this code in an online compiler and Code by Pabbly, and then show the difference in the results?

 

[JeffreyYu]

Done! Please see this loom here:

I think the <> is being parsed as a tag for some reason... there's also no way to escape it that I can find.

Loom | Free Screen & Video Recording Software

Use Loom to record quick videos of your screen and cam. Explain anything clearly and easily – and skip the meeting. An essential tool for hybrid workplaces.

www.loom.com

 

[ArshilAhmad]

Please allow us some time to look into this concern. We will get back to you with an update soon.

 

[JeffreyYu]

Sure, sounds good!

 

[Pabblymember11]

Hey @JeffreyYu

We've implemented some adjustments on our side, and we kindly ask you to test it out.

 

[JeffreyYu]

Got it! I'll try it out tomorrow.

I saw this deprecated the code step as well -- will this happen whenever the Python code is updated? if so, will we get an alert so we know to update our code steps? or will there be an update that will automatically update the step for us in the future?

 

[Pabblymember11]

We have departed the older version of Code bt Pabbly: Python action step and no it will not update itself if any changes were made.

However, if there are any major changes the action step could be deprecated and a new version will be introduced.

or will there be an update that will automatically update the step for us in the future?

At present, the notification for deprecation is part of our roadmap. We will keep you informed once it has been implemented.

 

[JeffreyYu]

Got it thank you!