Second proposed fix for the broken top_level.txt

[alexamici]

Minimal change that should fix #571. This time for real.

[joernhees]

sorry for asking, but can you point me to where it explicitly says we shouldn't use /? i tried finding something normative but failed...

[alexamici]

The relevant section is the one that I quoted in #571, you are supposed to include module names (dotted format) not folder paths and only top level modules. In fact setuptools drop all non top level module names and with my patch the top_level.txt file only include rdflib.

I noticed because for a project of mine I parsed the top_level.txt file of around a hundred projects and only rdflib and another project didn't conform to the documentation.

Finally, most projects just use setuptools.find_packages that does the job fine. Unless you have a reason not to, I'd advise you to use it as well. I can update the current PR if you wish.

[alexamici]

The Listing whole packages section of Writing the Setup Script of the main distutil documentation is also relevant.

The packages option tells the Distutils to process (build, distribute, install, etc.) all pure Python modules found in each package mentioned in the packages list. In order to do this, of course, there has to be a correspondence between package names and directories in the filesystem. The default correspondence is the most obvious one, i.e. package distutils is found in the directory distutils relative to the distribution root."

[joernhees]

Finally, most projects just use setuptools.find_packages that does the job fine. Unless you have a reason not to, I'd advise you to use it as well. I can update the current PR if you wish.

if this works, i would happily accept it... not really keen on manually doing stuff that can be done automatically... the setup process of rdflib grew and was tweaked over many years, so any simplification is welcome.

for now i'll accept this pull request, as what we currently do seems to be weird...