kicad-developers team mailing list archive

[Miguel Angel Ajo Pelayo <miguelangel@xxxxxxx>]

    I think I understand what you mean Dick, we need to provide a default way to compile and install python modules to a prefix, 
and also the set of default scripts & module libraries, & wizards, it's that what you mean?

    But anyway, when somebody installs a package system wide, we must provide our modules to them.

    Anyway, if you're talking about "pcbnew.py", for example, that should not be modified by humans, as it's
auto generated swig "mess" (nice and useful mess by the way) that get's rebuilt / overwritten by new compilation.

Miguel Angel Ajo
http://www.nbee.es
+34911407752
skype: ajoajoajo

On 11/03/2013, at 15:06, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:

> On 03/11/2013 08:25 AM, Adam Wolf wrote:
>> Miguel,
>> 
>> I only know about Blender/Python on Windows.
>> 
>> I think site-packages (dist-packages on Debian/Ubuntu) might be the
>> right way to do it.  Put the python modules in a place that's
>> already on the PYTHONPATH that package managers already expect folks
>> to put modules into.  The idea of having an environment variable to
>> tell CMake another place to put it is great, but I think
>> site-packages is a sane default.
> 
> I know of no python programmers named root.
> 
> No thanks.  My name is also not root.
> 
> So on my system, this would be considered extremely inconvenient.  I'd
> like to actually be able to edit the scripts.  If the intention is to
> make them not editable, then we should write them in C++ and compile them.
> 
> 
>