René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Backward incompatible API change toward 1.0","articleBody":"**DRAFT**\r\nThis issue is for write down my ideas.\r\n## Changing default behavior to use new spec.\r\n\r\nSee also: https://github.com/msgpack/msgpack/blob/master/spec.md#upgrading-messagepack-specification.\r\n\r\n### v1.0\r\n\r\nDrop `encoding` and `unicode_errors` option in Unpacker.  Add `raw=False` option instead.  When `raw=True` is passed, raw data in msgpack is deserialized into bytes object.\r\n\r\nDrop `encoding` and `unicode_errors` option in Packer.  Unicode is encoded with UTF-8 always.\r\n'surrogatepass' is not allowed to keep generated msgpack clean.  `use_bin_type=False` is the only way to create dirty (raw contains non UTF-8 data) msgpack.\r\n\r\n### v0.5.x\r\n\r\nAdd `raw=True` option to unpacker.\r\n\r\n### v0.6\r\n\r\n0.6 is version for warnings.\r\n\r\nPacker warns when `encoding` or `unicode_errors` is specified.\r\n\r\nUnpacker warns when `encoding` or `unicode_errors` is specified.  (\"Use raw=False  instead\").\r\n\r\n\r\n## PyPI package name\r\n\r\nIn past, easy_install crawls msgpack website and finds msgpack-x.y.z.tar.gz.  But it was for C.\r\nThat's why I moved from `msgpack` to `msgpack-python`\r\n\r\nSadly, pip doesn't support transitional package (empty, but depends on new name package).\r\nSo I release msgpack as both of msgpack-python and msgpack for a while until 1.0.\r\n\r\nAs 1.0, I release msgpack only.\r\n  ","author":{"url":"https://github.com/methane","@type":"Person","name":"methane"},"datePublished":"2016-05-05T02:09:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":22},"url":"https://github.com/191/msgpack-python/issues/191"}