It sounds strange though it's embarrassing.

I have a class with ClassMethods written in ISOS and Embedded Python.

The ClassMethods written in ISOS start in the Background as usual. No problems

But my 

ClassMethod setPy() [ Language = python ]
{
import iris, datetime, time
- - -

Just fails the JOB command with (even 15 sec) timeout and $ZC=0
This is not funny
My actual workaround:
I created a ClassMethod in ISOS, that does an elegant JobStart
and this ClassMethod only runs the Embedded Python ClassMethod.

You may have seen my series of articles on GlobalToJSON closing with Embedded Python.
And to me, Embedded means inside a Class and not PEX or other external variants.
The first variants showed that ePy is not an ultimate requirement. ISOS/COS may do it as well.
Here I try to position ePy inside IRIS.

In my article I described the work using iris.gref .
As the official documetation is rather slim on the subject it was necessary to dig into it.
Using the power of Python I was able to detect what I needed but was hidden.
I decided to share this with you. pydoc did the magic. 

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.  The rating reflects the experience of the reviewer with the status found at the time of review.  It is kind of a snapshot and might have changed meanwhile.   
New with this edition:
Reviews by other members of the community are marked by * in the last column.

This package was triggered by the extra bonus points in the contest for writing the example
in embedded Python only.  Therefore PURE

I will give you some additional information on my first embedded Python package.
it is written as a mix of python and ObjectScript to take the best of both worlds.

I have created a package to export a Global into JSON object file and to re-create it by reloading from this file
embeddedPython refers to the new available technologies. It should be understood as a learning exercise of 
how to handle the language interfaces. Only Global nodes containing data are presented in the generated JSON file.
Differently from the previous example, this one is using embedded Python only, no ObjectScript. Therefore PURE

I have created a package to export a Global into JSON object file and to re-create it by reloading from this file
embeddedPython refers to the new available technologies. It should be understood as a learning exercise of 
how to handle the language interfaces. Only Global nodes containing data are presented in the generated JSON file.

If one of your packages on OEX receives a review you get notified by OEX only on YOUR package.
It reflects my experience with the status I found at the time of my review.
It is kind of a snapshot and might have changed meanwhile.

I have created a package that offers a utility to load a Global into JSON object and reverse     
to create a Global from this type of JSON object. Compact refers to the structure created.
Globals nodes are included with data for a fast data load.   
But also the related code is quite compact.

I have created a package that offers a utility to load a Global into JSON object and reverse     
to create a Global from this type of JSON object. Efficient refers to the structure created.
Only Globals nodes containing data are presented in the generated JSON object.

I have created a package that offers a utility to load a Global into JSON object and reverse     
to create a Global from this type of JSON object. Academic refers to the structure created.
Each logical node of the Global is presented separately with all its descendants.
Even if they don't contain any stored data.

II try to explore the new SQL LOAD DATA  feature in SQL comparing it to SQL INSERT

I'm stuck at this point:  INSERT INTO <table> (columns...) VALUES  (.....)
allows having not just simple column references but also ALL Standard SQL FUNCTIONS (at least)
example:  

INSERT INTO Test (ShortName,DOB) VALUES  (SUBSTRING(Name,1,4),TO_DATE(displayDate,'MM-DD_YYY'))

This works perfectly. 
BUT the same VALUE clause applied to LOAD DATA  fails in various ways:

My personal problem is the use of DBeaver as a migration tool.
Especially as one of the strengths of IRIS ( and also Caché) before is the availability of the
SQLgateways that allow access to any external Db as long as for them an access using 
JDBC or ODBC is available. So I extended the package to demonstrate this.

If one of your packages on OEX receives a review you get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of my reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

If one of your packages on OEX receives a review you get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of my reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

Finding errors in your code or examining unexpected behavior is the main purpose of Debugging
I will try to refresh the traditional tools away from the helpers you have in Studio, VScode, Serenji, ....
to the basics which have been there before your preferred EDI used it in the background.

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of my reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

Just in case you never heard about OFX before
V1 was an attempt to create a dedicated SGML for banking and ignoring XML. Details.
It evolved to XML but not for M$ MONEY. Today we would use JSON for similar tasks.

I'm running reviews on Open Exchange since April 2021.
I have seen excellent packages, good ones, and some that made me feel just lost.
And I started to recognize contributors also by their style and organization of the submitted packages.
 

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

During the last weeks, I was working on various issues and problems related to SW development.
I found that quite often problem analysis was mostly chasing issues just on the surface
but not really attacking the deeper reasons of the problem and follow the consequences.
It's like the doc that stops your leg bleeding but doesn't see that it is broken.

In a former responsibility as Software Support Manager at Digital Equipment Corp. and
later CIO for Austria and Eastern Europe I trained successfully my product and operational 
specialists in analytic troubleshooting.

I'd like to share with you some storage features that also exist in Caché but are almost 
unknown and mostly not used. They are of course available in IRIS and gain importance
with large and distributed storage architectures.

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

I run most of my reviews using Docker Desktop on Windows 10.
According to the recommendations, I clean up docker and downloaded repositories after tests: 
Repos are simple but Docker is somewhat resistant to release the consumed disk space.

If you develop in IRIS you are confronted with two major phenomena:

• an incredibly fast and excellent designed data storage engine
• a scripting language to work on this storage engine, actually named ObjectScript 

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.

It is kind of a snapshot and might have changed meanwhile.
I also placed a bunch of Pull Requests on Github when I found a problem I could fix.
Some were accepted and merged, some just ignored. 
So if you did a major change and expect a changed review just let me know. 

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov  suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.
 

For several weeks I'm creating reviews on OEX.
So I'd like to explain to you the criteria that I apply to find my ratings.
Of course, each reviewer is an independent person and has his own criteria and his own opinion.
And that's good and important! As Winston Churchill once said:

"If 2 people always have the same opinion, then 1 of them is superfluous"