caronc / pynzbget Goto Github PK

PyNZBGet attempts to detect if the user is executing a script from the command line, or if they are calling it from within NZBGet. This detection can trigger a different series of events and can cause the script to out right fail if the wrong path is chosen in the wrong case.

This ticket executes this exact scenario.

You can now test your scripts from within NZBGet's Configuration page. Tie this into this framework plugin.

The syntax within the NZB-Get script looks like this

############################################################################
### OPTIONS                                                              ###

#
# To check connection parameters click the button.
# ConnectionTest@Send Test E-Mail
#
#
# ...

In the above example, a button will appear on the NZBGet's script configuration screen that reads Send Tests E-Mail. When the button is pressed, the script is executed with the environment variable NZBCP_COMMAND with the value ConnectionTest.

if None is passed in, then debugging should be turned off.

Add support for PID-File management and unique process instance detection so that Scheduler scripts can run indefinitely (or until NZBGet signals them to close). NZBGet will signal when it is shut down or performs a Reload.

With respect to issue resolved here, it is possible to get a DownloadedSizeMB KeyError when accessing NZBGet's Control API.

A question mark plays a roll in the parsing of the URL message itself, a url containing a password with a question mark has been reported to break pynzbget:

eg: proto://user:pass.with.?is.failing@host

I love the scripts you create;

Will there be any python 3.x support for your scripts/framework?

thanks

SABnzbd supports environment variables with their Post Processing scripts documented here. Add support to pynzbget allowing posts process scripts written for NZBGet to also be compatible with SABnzbd.