SUSE Package Hub 15 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-Standard-Pool Package Hub 15 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-Standard-Pool Package Hub 15 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 SP1 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP1-Backports-Pool Package Hub 15 SP1 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 SP1 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP1-Backports-Pool Package Hub 15 SP1 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 SP2 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP2-Backports-Pool Package Hub 15 SP2 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 SP2 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP2-Backports-Pool Package Hub 15 SP2 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 SP3 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP3-Backports-Pool Package Hub 15 SP3 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: SUSE Package Hub 15 SP3 one-click install Install python-interlude NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP3-Backports-Pool Package Hub 15 SP3 Dummy repo - this will fail python-interlude Interlude for Doctests provides an Interactive Console Provides an interactive shell aka console inside your doctest case. The console looks exact like in a doctest-case and you can copy and paste code from the shell into your doctest. It feels as you are in the test case itself. Its not pdb, it's a python shell. In your doctest you can invoke the shell at any point by calling:: >>> interact( locals() ) To make your testrunner interlude aware following is needed: