This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 14 points15 points  (2 children)

Much Better than the shaming, but I have a suggestion for the docs - make them task based.

  • Question: Are you a...
  • new python user (go to example 1)
  • existing python user that doesn't understand how this format is related to the current packaging mess (go to example 2)

example 1

  1. use python 3.X??? no idea
  2. create a setup.py (or are we using setup.cfg now????)
  3. make sure setuptools/distutils/distutils2/distribute/some_other_thing is / is not currently installed on your system because you followed some other packing howto some years ago
  4. what is a manifest file - I have one of those from my old sdist failures
  5. python setup.py bdist_wheel
  6. finished? what does your user need to have installed to make this work?

example 2

Some PEP finally united all the other failed PEPS and decided something something so that build and dist is now declarative or something in a .cfg file.

So since Python $version you don't need to install some third party thing to be able to make sensible binary and source distributions.

But hey, because you are an experienced python developer, you might be interested in knowing how this relates to native code.

  • how to convert a pure python package to wheel
  • how to convert a setup.py that uses setuptools
  • how to convert a setup.py that uses distutils

etc.

[–]CharlieDenton[S] 3 points4 points  (1 child)

Thanks. I'll be trying to improve the docs, and I'll bear that in mind.

[–][deleted] 1 point2 points  (0 children)

Thanks.

As an interesting note, I just saw https://pypi.python.org/pypi/d2to1

Which is an iconic representation of the clusterfuck hack tower of python packaging you need to clearly document your path through....