lp://staging/~cjwatson/storm/clarify-no-allow-none-default-none-exception

Created by Colin Watson and last modified
Get this branch:
bzr branch lp://staging/~cjwatson/storm/clarify-no-allow-none-default-none-exception
Only Colin Watson can upload to this branch. If you are Colin Watson please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Colin Watson
Project:
Storm
Status:
Merged

Recent revisions

576. By Colin Watson

Clarify exception for a property with allow_none=False and default=None.

Creating a property with `allow_none=False, default=None` doesn't make
sense, but it's sometimes easy to set things up that way by accident
during refactoring. Storm immediately raises `NoneError` when creating
the variable in that case. However, it's not obvious that the exception
is due to the bad default, and I spent some time with a colleague today
debugging a situation that turned out to be due to this.

Change the exception message from "None isn't acceptable as a value" to
"None isn't acceptable as a default value" in this case, to clue future
travellers into the fact that the problem relates to the default.

575. By Colin Watson

[r=cjwatson] Fix a typo in the tutorial doctest code block

574. By Colin Watson

[r=ilasc] Fix test compatibility with MySQL >= 8.0.24.

573. By Colin Watson

Bump version to 0.25.0.99.

572. By Colin Watson

Avoid traceback reference cycles when wrapping exceptions. [r=ilasc]

571. By Colin Watson

Release Storm 0.25.

570. By Colin Watson

Fix MANIFEST.in prune syntax.

569. By Colin Watson

[r=ilasc] Support Python 3.9.

568. By Colin Watson

[r=ilasc] Restore MySQL support.

567. By Colin Watson

[r=ilasc] Fix py27 and py35 tox environments.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp://staging/storm
This branch contains Public information 
Everyone can see this information.

Subscribers