Torsten Landschoff

> Is this responsible for getting random INFO lines after the pytest summary when using `logging.basicConfig(level=logging.INFO); pytest.main(['--log-cli-level', 'warning'])` and `python` instead of `python -u`? Testcase: No. This was about stdout/stderr...

This seems to boil down to this behaviour wrt. customize: ```python $ python Python 2.7.12 (default, Nov 4 2017, 00:30:53) >>> import decimal >>> from spyne import Uuid >>> from...

AFAICT this `is_default` basically exists solely for the purpose of filtering duplicate types. Therefore I'd think this should work or be dropped altogether , leaving it to the XML generation...

We forked at spyne 2.9.3 and ported it to Python 3 ourselves (at least in so far that our unit and integration tests are running). As we are no longer...

BTW: This can be worked around by explicitly giving the namespace like this: ```python UUIDType = Unicode( type_name="UUIDType", pattern=r"[A-Fa-f0-9]{8}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{12}", __namespace__="expected.namespace", ) ``` This makes the wsdl of spyne 2.9 and...

FYI: The behaviour in spyne master at 049b7899b6498346a3a1d74e58fa55b7cfe24abc is unchanged.

*Edit*: Simplified the stack trace, dropping pytest and debugger frames. > this could be the result of calling resolve_namespace() too early somewhere. You bet. Here is the traceback of that...

I guess it's more about how many people care about the generated WSDL. After all, whatever the namespace, this would stil work.

BTW: I just noted this comment in resolve_namespace: ``` def resolve_namespace(cls, default_ns, tags=None): """This call finalizes the namespace assignment. The default namespace is not available until the application calls populate_interface...

We got bitten by this too. Builds that used to work (on CentOS 5, CentOS 6) still seemed to work but the final PyInstaller build does not work.