I am working on autodesk flame for over 10 years on commercials and feature films. On my first Nuke job I had a client approved edit (yes, this was nearly true) and no system available to me to assemble the edit in a form of DPX sequences.
So I set up (kind of) this script by hand and more than once miscalculated with the TimeOffsets (I set them up in the read node as 'frame-xxx'). This script is not supposed to be a conforming tool.
But often I set up a job on flame, conform it and then pass out all the shots on a server for the 2D and 3D departments in a form of SH01 to SHxx...in this case I had a reference quicktime movie, I added frame numbers to it which makes it easy to count all the editpoints in the spot.
Example: (1500 frames edit with 10 shots) in the file 'editpoints_1500.txt'
Use a fresh and clean Nuke with no nodes in the DAG!
create an "editpoints.txt" file
Have your shots stored in subfolders from sh01 to shxx. (shxx is only the last frame)
And tell the script your file format.
This will create 'read' nodes with their 'timeoffset' and 'switch' nodes which jump from shot to shot.
As this is my first script I left all my debugging print commands inside the script.
If you comment out all nuke commands you can run this script "dry" as pure Python.
This script can be run directly from the script editor or run from your custom menu entry.
toodee.addCommand('AssembleEdit', 'AssembleEdit.AssembleEdit()', icon="/yourpath/AssEdit.png")