add py_binary rule for console_scripts

[chaoran]

Add py_binary rule if there is console_scripts entry_point defined for the package.

[Globegitter]

ping @apt-itude would be a nice one to have

[Globegitter]

we need to provide main = "bin/{entry_point}.py" here, because in the case when {rule} has bin- prepended it won't match automatically.

[chaoran]

Added. Thank for catching that.

[Globegitter]

@chaoran not sure if you also ran into the issues but it seems py_binary targets are causing issues, see: bazelbuild/bazel#7091 (comment)

[chaoran]

@Globegitter Yes, I just tried to run bazel run @pip_deps//pytest:bin-pytest. It gave me an error ImportError: module 'pytest' has no attribute 'main'. I was using a python library that happen to not use the same name for the library and binary file, which didn't cause me any trouble. But, anyway, I gradually start to realize that using python with bazel is lost hope. I'm waiting for Google to support python in bazel natively before I do something serious with it.

BTW I guess adding a genrule to rename the binary xxx.py file to bin-xxx.py would workaround the issue? I haven't tried it yet.

[Globegitter]

@chaoran - the way I got around this is by providing a patch functionality to a forked version of rules_pip. See ecosia@adce162

Yeah hopefully it keeps on improving over the coming weeks/months. Now with the toolchain support there is not much missing anymore from getting it to work nicely in an OSS environment.