Closed AlexWaygood closed 1 year ago
Is package_data
merged with what MANIFEST.in
brings in? If not, we'll just want include babel/py.typed
in the manifest...
Nope, yep, this does exactly what it should ๐
Merging #975 (4743881) into master (f5bb5bf) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #975 +/- ##
=======================================
Coverage 90.91% 90.91%
=======================================
Files 25 25
Lines 4350 4350
=======================================
Hits 3955 3955
Misses 395 395
:mega: Weโre building smart automated test selection to slash your CI/CD build times. Learn more
Thanks!
Is
package_data
merged with whatMANIFEST.in
brings in? If not, we'll just want includebabel/py.typed
in the manifest...
I... hope so. If I'm honest, I'm young enough that I've never maintained a project that uses a MANIFEST.in
file or uses setuptools
as a build backend (I generally just use hatchling
).
@AlexWaygood Thanks again. Released in Babel 2.12.1, now on PyPI.
Confirmed that mypy recognises the library as having inline type annotations with the latest release ๐
934 by @DenverCoder1 added inline type annotations and a
py.typed
file, which is great! Unfortunately, however, thepy.typed
file hasn't been included in wheels published to PyPI for v2.12.0. This means that if Ipip install
babel locally, mypy still doesn't recognisebabel
as a typed library. Running mypy on a file with justimport babel
in it results in this output from mypy (unless the typeshedtypes-babel
package is installed):The fix is simple: just a one-line addition to
setup.py
.Closes #795 (which should maybe have been closed after #934).