Indeed I see :), but to be clear, I'm not against the try/else idiom, I'm against "implicitness". In this case, it was regarding "implicit None return", and making it explicit the way I suggested was going to go against the "don't use things that were created in a deeper level/scope than the current one".

An alternative that complies to both of our OCD craziness would be:

```python
    period_str = os.environ.get(INCOMING_CHECK_PERIOD_ENV, None)

    try:
        period = int(period_str)
    except ValueError, TypeError:
        logger.warning("BAD value found for %s: %s" % (
            INCOMING_CHECK_PERIOD_ENV,
            period_str))
    except Exception as exc:
        logger.warning("Unhandled error while getting %s: %r" % (
            INCOMING_CHECK_PERIOD_ENV,
            exc))
    else:
        return period

    return None
```