Problem working with .py files

[BG Davis]

I opened a file with Avidemux and did edits.
I saved as py file.
I then opened a different py file to work on it.
Avidemux crashed.  When I tried again to open the second py file to work on it I got the first error message (attached).
When I pressed OK I got the second error message (attached).
When I pressed OK I got the third error message (attached).

When I reopened, I got the Avidemux crash file message.
Here is the crash file:

ADM_setCrashHook [libADM_core6.dll]
ADM_setCrashHook [libADM_core6.dll]
ADM_backTrack [libADM_core6.dll]
ADM_Composer::addSegment(unsigned int, unsigned long long, unsigned long long) [avidemux.exe]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
unknown function [libADM_script_tinyPy.dll]
A_appendVideo(char const*) [avidemux.exe]
A_openVideo(char const*) [avidemux.exe]
ADM_QT4_fileSel::GUI_FileSelReadExtension(char const*, char const*, void (*)(char const*)) [avidemux.exe]
HandleAction(Action) [avidemux.exe]
MainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [avidemux.exe]
QMetaObject::activate(QObject*, int, int, void**) [Qt5Core.dll]
MainWindow::actionSignal(Action) [avidemux.exe]
MainWindow::searchFileMenu(QAction*) [avidemux.exe]
MainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [avidemux.exe]
QMetaObject::activate(QObject*, int, int, void**) [Qt5Core.dll]
QMenu::setIcon(QIcon const&) [Qt5Widgets.dll]
QMenu::leaveEvent(QEvent*) [Qt5Widgets.dll]
QMenu::mouseReleaseEvent(QMouseEvent*) [Qt5Widgets.dll]
QWidget::event(QEvent*) [Qt5Widgets.dll]
QMenu::event(QEvent*) [Qt5Widgets.dll]
QApplicationPrivate::notify_helper(QObject*, QEvent*) [Qt5Widgets.dll]
QApplication::notify(QObject*, QEvent*) [Qt5Widgets.dll]
QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) [Qt5Core.dll]
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) [Qt5Widgets.dll]
QDesktopWidget::qt_metacall(QMetaObject::Call, int, void**) [Qt5Widgets.dll]
QDesktopWidget::qt_metacall(QMetaObject::Call, int, void**) [Qt5Widgets.dll]
QApplicationPrivate::notify_helper(QObject*, QEvent*) [Qt5Widgets.dll]
QApplication::notify(QObject*, QEvent*) [Qt5Widgets.dll]
QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) [Qt5Core.dll]
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) [Qt5Gui.dll]
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) [Qt5Gui.dll]
QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) [Qt5Gui.dll]
QEventDispatcherWin32Private::sendTimerEvent(int) [Qt5Core.dll]
TranslateMessageEx [USER32.dll]
TranslateMessage [USER32.dll]
QEventDispatcherWin32::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) [Qt5Core.dll]
qt_plugin_instance [qwindows.dll]
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) [Qt5Core.dll]
QCoreApplication::exec() [Qt5Core.dll]
UI_RunApp() [avidemux.exe]
startAvidemux(int, char**) [avidemux.exe]
SDL_main [avidemux.exe]
ms2timedisplay(unsigned int) [avidemux.exe]
unknown function [avidemux.exe]
unknown function [avidemux.exe]
BaseThreadInitThunk [kernel32.dll]
RtlUserThreadStart [ntdll.dll]

[eumagga0x2a]

The other .py file specified a segment layout not matching the currently load videos.

Please clarify the problem with the latest nightly., 2.7.2 is < last release and thus unsupported.

[BG Davis]

Thanks for responding.
I prefer to avoid v.2.6.3 since it failed to function properly for me.  Maybe in a few weeks when it has undergone more use an scrutiny.
So I guess this issue will have to wait until then.

[eumagga0x2a]

In a few weeks there will be a 2.7.4