Angelo Gladding
Angelo Gladding
The singular instance is here: https://github.com/microformats/mf2py/blob/8f72a81cb37934796939270116b7b7b7de888f88/mf2py/parser.py#L129-L143 `requests`' stability makes for a sensible default. Here's what you'd currently have to use to leverage a different library: ```python import httpx url =...
Should we press a 1.1.3 or 1.2 release before moving to 2.0? https://packaging.python.org/en/latest/guides/dropping-older-python-versions/ describes using `python_requires` in setup.py to properly signal the deprecation -- eg. add python_requires='>=2.7' to a final...
https://github.com/microformats/mf2py/compare/main...angelogladding:mf2py:final-py2 is a start
https://stackoverflow.com/a/56135899/6841359 describes bumping semver minor for a mark of deprecation--so jump to v1.2? Also, do we need to add a deprecation message to the README? 2.7 has been EOL since...
Yes the deprecation of EOL python versions should come first. Modern systems won't support =2.7` metadata added: https://github.com/microformats/mf2py/pull/187/commits/b07418f70ec14aa8afe410453bd12f8296e45c62 Then we can actually remove python2 support https://github.com/microformats/mf2py/pull/179/commits/78c8f7ff87225df764ff6c16addf2a65d41a982a and continue with the...
I wasn't sure how much I'd be able to contribute so I just gave it a whirl over at https://github.com/canopy/mf2py - switched to pyproject.toml via poetry - switched from nose...
I think we can all agree we need to: - Release a final Python 2.7 package and document deprecation - Switch from nose2 to pytest - Deprecate Python 2 support...
@sknebel do you mean something like this: in reply to: Main thread This is the <body> of a comment. parses to: { 'items': [{ 'type': ['h-entry'], 'properties': {'in-reply-to': ['//example.com/foo'], 'content':...
"First of all, speculation that we did not anticipate CC0 usage for software at the time is true." https://web.archive.org/web/20150906005825/https://lists.opensource.org/pipermail/license-review/2012-February/000231.html Both of the following are OSI approved public-domain-equivalent licenses: - https://en.wikipedia.org/wiki/MIT_License#MIT_No_Attribution_License...
For what it's worth I'll bless a license change of the code to `0BSD`. I'm not sure there's any point in dual licensing under different public-domain-equivalents. It only complicates things....