On Sunday, 21 August 2016 16:23:13 BST Ralph Corderoy wrote:
> Going back to your first mail, there's three ways of running it.
>
> > #!/usr/bin/env python
>
> ...
>
> > #!/usr/bin/env python2.7
>
> ...
>
> > Python 2.7.12 (default, Jul 1 2016, 15:12:24)
>
> For the
Hi Terry,
> Well actually it was in the first line of the shell output at runtime:
>
> Python 2.7.12 (default, Jul 1 2016, 15:12:24)
Going back to your first mail, there's three ways of running it.
> #!/usr/bin/env python
...
> #!/usr/bin/env python2.7
...
> Python 2.7.12
On Sunday, 21 August 2016 15:53:47 BST Terry Coles wrote:
> > Add `import logging' to your other imports, and then immediately after
> > try `logging.basicConfig()'.
>
> I've done that and am currently waiting for the next schedule job to occur
> (1600). Where should I expect the logger to write
Hi Terry,
> No handlers could be found for logger "apscheduler.scheduler"
It's handy for Python questions to state whether it's 2 or 3. :-)
Running Python in the same method as your script with its --version
option will say.
Add `import logging' to your other imports, and then immediately
Hi,
Most of you are aware by now that Clive and I have a project to bring the
bells back to the Wimborne Model Town Minster. I've been experimenting with
using apscheduler and mpg321 in Python to realise this. It's pretty crude at
the moment, but if I run two separate programs (the bells and
5 matches
Mail list logo
