| 1 |
On Tue, 9 Feb 2016 14:53:52 -0500 |
| 2 |
Ian Stakenvicius <axs@g.o> wrote: |
| 3 |
|
| 4 |
> On 09/02/16 02:51 PM, Michał Górny wrote: |
| 5 |
> > Hello, everyone. |
| 6 |
> > |
| 7 |
> > After all those boring, meaningless and violent mailing list |
| 8 |
> > threads, here's something nice and simple. I'd like to find a new |
| 9 |
> > nice name for the C wrapper part of python-exec2, and I would like |
| 10 |
> > to ask you for ideas. |
| 11 |
> > |
| 12 |
> > For some explanation, python-exec2 consists of two wrappers. One of |
| 13 |
> > them is the 'core' C wrapper that does most of the work. The other |
| 14 |
> > is a Python script with special shebang that is used to keep |
| 15 |
> > 'python /usr/bin/foo' working while deferring direct executions to |
| 16 |
> > the C wrapper. |
| 17 |
> > |
| 18 |
> > The Python wrapper is installed as /usr/lib/python-exec/python-exec2 |
| 19 |
> > and this can't change since everything is symlinked to it. The C |
| 20 |
> > wrapper is named python-exec2-c (which is an ugly name), and since |
| 21 |
> > it's used only internally, I can safely change its name to |
| 22 |
> > something nicer. |
| 23 |
> > |
| 24 |
> > Any ideas? If possible, I'd like to avoid ambiguity between the two |
| 25 |
> > wrappers, so the C counterpart would have to be highlighted somehow. |
| 26 |
> > |
| 27 |
> |
| 28 |
> python-exec-cwrapper ? |
| 29 |
> |
| 30 |
|
| 31 |
NO, No, you mistyped it... |
| 32 |
|
| 33 |
python-exec-crapper |
| 34 |
|
| 35 |
:O |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Brian Dolbec <dolsen> |
| 40 |
|
| 41 |
P.S. just finning with you :) |
Archives