Re: [Distutils] Interrogate distribution for an entry point command path

It does not store that information, except maybe in the manifest used for uninstall in the .*-info directory for your installed distribution. On Sat, Oct 15, 2016, 19:39 Ben Finney wrote: > Thomas Kluyver writes: > > > If the entry point looks

[Distutils] Commit 17f89f4 "Update sdist to use sdist_add_defaults forward compatibility"

Hi Jason, I just started looking at the setuptools repo last night to see if I could figure out why setuptools doesn't place data_files inside an sdist and I saw your commit 17f89f4 to teach the sdist command to use the python 36 compatibility behavior. But it overrides

Re: [Distutils] Interrogate distribution for an entry point command path

Thomas Kluyver writes: > If the entry point looks like: > > foo=foomod:main > > Then you can invoke it in a subprocess by running: > > subprocess.Popen([sys.executable, '-c', 'import foomod; foomod.main()']) That will invoke the program. I'll probably try that. One

Re: [Distutils] Interrogate distribution for an entry point command path

On Sat, Oct 15, 2016, at 06:57 PM, Ben Finney wrote: > I'm modifying an existing application that invokes the program as a > subprocess, so I'm wanting to find that program as an external command. If the entry point looks like: foo=foomod:main Then you can invoke it in a subprocess by running:

Re: [Distutils] Commit 17f89f4 "Update sdist to use sdist_add_defaults forward compatibility"

The discussion started here: https://github.com/pypa/setuptools/pull/750 Basically, I don’t understand exactly why that functionality was disabled, but I give my best guess in that ticket - mainly that I think data_files is incompatible with encapsulated installs, so I suspect it was

Re: [Distutils] Interrogate distribution for an entry point command path

Nick Timkovich writes: > 1. include the shell scripts (could also be binaries) in the package & > manifest > (https://github.com/nicktimko/autolycus/blob/master/MANIFEST.in#L3) No, I'm using ‘[…] install --install-scripts=APPLICATION_SCRIPTS_PATH’ at install time. > 2.

Re: [Distutils] Interrogate distribution for an entry point command path

I recently was trying to port a mix of shell & Python scripts to pure Python (https://github.com/nicktimko/autolycus), and my interim solution to get something working to test was to: 1. include the shell scripts (could also be binaries) in the package & manifest

Re: [Distutils] Interrogate distribution for an entry point command path

Nick Timkovich writes: > Usually that entry point is on the PATH […] It's not, because I'm deliberately specifying that it shouldn't be, at install time. This is an executable that is private to the application and not for general availability on the host. > If you

Re: [Distutils] Interrogate distribution for an entry point command path

Usually that entry point is on the PATH, so it should be somewhere in os.environ['PATH'], so if you just `subprocess.run(['myentrything'])` that would fire it. If you want to call that entry point from your code, the clean way (same environment/version, and especially if you don't need to bother

[Distutils] Interrogate distribution for an entry point command path

Howdy, How can a Python application discover at run-time where on the filesystem its own ‘entry_points’ programs are available? The Setuptools ‘entry_points’ are available at run-time to the distribution, via the ‘pkg_resources’ API for entry points