@@ -59,7 +59,7 @@ upgrade.
5959
6060## As a user
6161
62- ### Install Pip 9.0
62+ ### Install pip 9.0
6363
6464If you are already a Python 3 user, you should not encounter a lot of
6565disruption. Please still check that the libraries you use follow best practices
@@ -172,7 +172,7 @@ this](https://github.com/pypa/pypi-legacy/pull/506).
172172Thus as long as your user have recent enough versions of pip and setuptools
173173they will get the right version of your library.
174174
175- # Unit Testing and documentation
175+ # Unit testing and documentation
176176
177177It is recommended ** not** to invoke ` setup.py ` directly either with ` install ` or
178178` develop ` subcommands. These may not correctly resolve dependencies, and can
@@ -182,7 +182,7 @@ install .` and `pip install -e .` for regular and developer installs, respectiv
182182Check in scripts and documentation that the correct installation command is
183183used.
184184
185- # Recommended Mitigations
185+ # Recommended mitigations
186186
187187These are not mandatory but should make the transition seamless by warning your
188188users early enough _ and_ providing useful error messages.
@@ -273,7 +273,7 @@ The regular expression to check for validity of pep440 can be found below:
273273 (\\.dev(0|[1-9]\\d*))?
274274
275275
276- ## fail early in setup.py
276+ ## Fail early in setup.py
277277
278278Leave ` setup.py ` python 2 compatible and fail early. If you detect Python 2
279279raise a clear error message and ask the user to make sure they have pip > 9.0 (or
@@ -296,7 +296,7 @@ and that you will hear about. This is an attempt to acknowledge them, and
296296explain why they can't work and what are their drawbacks before you attempt to
297297implement them.
298298
299- ### Use a meta-package.
299+ ### Use a meta-package
300300
301301It is possible to release a meta-package that has _ virtually_ no code and relies
302302on a conditional dependency to install its actual core code on the user system.
@@ -329,16 +329,16 @@ publish multiple sdist of a package targeting various python version.
329329It is not possible anymore to upload multiple sdist files on PyPI, so this
330330solution is no longer tenable.
331331
332- ### Wheel only ?
332+ ### Wheel only?
333333
334334Releasing a package only using wheels for a given python version is doable, but
335335this will break downstream packages that may require the original source to
336336reproduce their build.
337337
338- # Why all * this* ?!?
338+ # Why all * this* ?!?
339339
340340You might wonder why all this, it's 2018 already, so how come this is still an
341- issue? Python 3 has been out for 9+ years now !
341+ issue? Python 3 has been out for 9+ years now!
342342
343343Well there are many reasons for this. First of all, this issue mostly affects
344344libraries that are currently python 2 and Python 3 compatible at the same time.
0 commit comments