In article ,
Louis Theran wrote:
>
>Is there a standard recipe for getting distutils to built universal .so
>files for modules that have C/C++ source?
You should check the archives of
http://mail.python.org/mailman/listinfo/pythonmac-sig
--
Aahz (a...@pythoncraft.com) <*> http
On 7/26/10 1:36 PM, Louis Theran wrote:
Is there a standard recipe for getting distutils to built
universal .so files for modules that have C/C++ source?
If your Python was built to be Universal, it will automatically use the same
architecture flags to build the extension modules Universal.
Is there a standard recipe for getting distutils to built
universal .so files for modules that have C/C++ source?
--
http://mail.python.org/mailman/listinfo/python-list
Hi there,
I'm having problems with creating an installer for a module of mine by
using distutils. I'll try to explain my problem as clear as I can
(sorry but English is not my first language).
This is the structure of my module:
setup.py
mypackage/
__init__.py
Thanks everyone, for your answers. They've been very helpful.
Keith
--
http://mail.python.org/mailman/listinfo/python-list
Robert Kern wrote:
> Instead, include the default data inside the package (read-only to non-root
> users). Then allow the script itself to create the directory the first time
> it
> is run (read-write, and it should then automatically be accessible to the
> user
> that ran the script). You mi
Keith Perkins wrote:
>
> On a similar note , I have another question about distutils and data files.
> I have a little program that uses a txt file to store data, and it works
> fine running it in it's own folder, if I install through distutils, using
> sudo to get it to write to the site-packages
Keith Perkins wrote:
> I did install it in ~/.script/data.txt, and distutils set the
> user/group as root. Is it impossible to install this with distutils?
> Since I'm running setup as root, should I just add a class or method to
> chown the datafolder/file to the installer. Should I use autotool
On Fri, 29 Sep 2006 18:57:12 -0500, Robert Kern wrote:
> Keith Perkins wrote:
>
>> On a similar note , I have another question about distutils and data files.
>> I have a little program that uses a txt file to store data, and it works
>> fine running it in it's own folder, if I install through di
Keith Perkins wrote:
> On a similar note , I have another question about distutils and data files.
> I have a little program that uses a txt file to store data, and it works
> fine running it in it's own folder, if I install through distutils, using
> sudo to get it to write to the site-packages f
On Fri, 29 Sep 2006 13:53:46 -0400, Eric S. Johansson wrote:
> is there anyway I can, in a setup.py file, set and internal equivalent
> to the '--install-scripts' commandline option?
>
> script installation directory but I don't want on the command line where
> things can go horribly wrong if
Eric S. Johansson wrote:
> So what I have seen so far says that to be able to take data from a
> series of directories scatter it to other directories may be out of
> scope. It's okay. If I have to write a wrapper, it won't be the first
> time.
do'h.
http://docs.python.org/dist/node13.html
Robert Kern wrote:
> Eric S. Johansson wrote:
>
>> Now I get to puzzle out how to install the CGI plus images plus
>> stylesheets plus plus plus mess. Probably a bit outside of the scope of
>> distutils even if the CGI programs are Python. ;-)
>
> I recommend installing the data inside the pa
Eric S. Johansson wrote:
> Now I get to puzzle out how to install the CGI plus images plus
> stylesheets plus plus plus mess. Probably a bit outside of the scope of
> distutils even if the CGI programs are Python. ;-)
I recommend installing the data inside the package itself. In 2.4, use the
Robert Kern wrote:
>
> Okay, if it's just for internal use, then I certainly have no objection. Use
> a
> setup.cfg file:
>
>http://docs.python.org/inst/config-syntax.html
>
> Specifically, use something like the following section:
>
> [install]
> install_scripts=/path/to/scripts/director
Eric S. Johansson wrote:
> Robert Kern wrote:
>> Eric S. Johansson wrote:
>>> is there anyway I can, in a setup.py file, set and internal equivalent
>>> to the '--install-scripts' commandline option?
>> Please don't. Hard-coding that interferes with the user's decision of where
>> things should
Robert Kern wrote:
> Eric S. Johansson wrote:
>> is there anyway I can, in a setup.py file, set and internal equivalent
>> to the '--install-scripts' commandline option?
>
> Please don't. Hard-coding that interferes with the user's decision of where
> things should go. Only the user should be m
Eric S. Johansson wrote:
> is there anyway I can, in a setup.py file, set and internal equivalent
> to the '--install-scripts' commandline option?
Please don't. Hard-coding that interferes with the user's decision of where
things should go. Only the user should be making that decision, not the
is there anyway I can, in a setup.py file, set and internal equivalent
to the '--install-scripts' commandline option?
script installation directory but I don't want on the command line where
things can go horribly wrong if the user forgets. I would like to
create a new default setting for th
Joachim Dahl wrote:
> E.g., say I want to compile a project as:
>
> gcc -Ddef1 -c foo.c -o foo_def1.o
> gcc -Ddef2 -c foo.c -o foo_def2.o
> gcc foo_def1.o foo_def2.o -o myext_module.o
>
> How would I do that using distutils? It doesn't seem to be possible with
> the normal core.setup method, and d
On Wed, 07 Sep 2005 10:56:40 -0700, Joachim Dahl <[EMAIL PROTECTED]> wrote:
> I am trying to make a customized install script for an extension module
> using the distutils.ccompiler class.
>
> I want to embed an existing makefile for the C libraries into the Python
> setup script, but I am not su
Peter Hansen wrote:
>>How how can I install my .mo files from a distutil script into its
>>default location?
>>
>>sys.prefix + os.sep + 'share' + os.sep + 'locale'
>>
>>
>
>I can't answer the first question, but the latter should be written this
>way instead
>
>os.path.join(sys.prefix, '
Laszlo Zsolt Nagy wrote:
> How how can I install my .mo files from a distutil script into its
> default location?
>
> sys.prefix + os.sep + 'share' + os.sep + 'locale'
I can't answer the first question, but the latter should be written this
way instead
os.path.join(sys.prefix, 'share', 'lo
How how can I install my .mo files from a distutil script into its
default location?
sys.prefix + os.sep + 'share' + os.sep + 'locale'
--
http://mail.python.org/mailman/listinfo/python-list
I am trying to make a customized install script for an extension module
using the distutils.ccompiler class.
I want to embed an existing makefile for the C libraries into the Python
setup script, but I am not sure what's the right way to do it...
E.g., say I want to compile a project as:
gcc -
Hey guys,
I wrote a fairly simple program that has 3 python files, and needs a
couple directories created to run. It also uses PythonCard. I would
like make it easily distributable to users who already have Python
installed. Would anyone mind explaining this in easy to follow steps
or pointing
If the environment variable:
os.environ['APPDATA']
is present on non-English Windows, you may be able to use that to get
what you need.
john
--
http://mail.python.org/mailman/listinfo/python-list
I'm trying to package a windows app with distutils (you've heard about
it before). The app needs to store some data on disk and apparently
the right place to put it is in the "Application Data" directory. The
only way I see to find out the name of this directory is the
get_special_folder_path fun
Le 16 Apr 2005 01:20:34 -0700, Qiangning Hong a écrit :
> To avoid namespace confliction with other Python packages, I want all
> my projects to be put into a specific namespace, e.g. 'hongqn' package,
> so that I can use "from hongqn.proj1 import module1", "from
> hongqn.proj2.subpack1 import modu
To avoid namespace confliction with other Python packages, I want all
my projects to be put into a specific namespace, e.g. 'hongqn' package,
so that I can use "from hongqn.proj1 import module1", "from
hongqn.proj2.subpack1 import module2", etc.
These projects are developed and maintained and dist
To avoid namespace confliction with other Python packages, I want all
my projects to be put into a specific namespace, e.g. 'hongqn' package,
so that I can use "from hongqn.proj1 import module1", "from
hongqn.proj2.subpack1 import module2", etc.
These projects are developed and maintained and dist
31 matches
Mail list logo