Am 12.09.2014 19:15, schrieb Erik Bray:
On Fri, Sep 12, 2014 at 8:38 AM, Thomas Heller thel...@ctypes.org wrote:
[snip about strange .pth files installed for namespace packages]
Hi Thomas,
I've dealt with this issue myself extensively in the past, but it's
been a while so I might have
Am 12.09.2014 21:24, schrieb Eric V. Smith:
[Oops, replying to the list this time. Sorry for the dupe, Thomas.]
On 9/12/2014 3:14 PM, Thomas Heller wrote:
So it seems that it is a bug in setuptools: It must not create or
install these pth files when installing in Python 3.3 or newer (which
Am 21.03.2014 20:19, schrieb Daniel Holth:
2. You are correct. We plan to switch the default to be py3-none-any
runs on some Python 3 interpreter. cp33 means only runs on CPython
however we have decided this tag is probably less useful than
initially posited since there are other ways to say has
Am 31.01.2014 09:35, schrieb Vinay Sajip:
Thomas Heller theller at ctypes.org writes:
It uses the _memimporter extension which uses code from Joachim
Bauch's MemoryModule library. This library emulates the win32 api
function LoadLibrary.
When this was mentioned on python-dev last March you
on that case. I
suspect that the issues are similar but I defer to the platform
experts.
[3] There is, I believe, code out there on the internet to map a DLL
image into a process based purely in memory, but I think it's a fairly
gross hack. I have a suspicion that someone - possibly Thomas Heller
I'm trying out to submit a wheel to testpypi.python.org and then
install it from there with pip. It doesn't work; what does the
following error message mean?
c:\py -3.4 -m pip install py2exe -r https://testpypi.python.org/pypi/
Exception:
Traceback (most recent call last):
File
Am 23.01.2014 10:05, schrieb Paul Moore:
On 23 January 2014 08:28, Thomas Heller thel...@ctypes.org wrote:
I'm trying out to submit a wheel to testpypi.python.org and then
install it from there with pip. It doesn't work; what does the
following error message mean?
c:\py -3.4 -m pip install
After having used and built bdist_wininst installers for years (well, I
should say decades) I have recently started playing with pip.
In theory, it is a grat solution. Respects virtual environments
(although I haven't tested them yet), allows to freeze to a requirements
file, and so on.
It
Am 23.01.2014 13:16, schrieb Paul Moore:
On 23 January 2014 11:48, Thomas Heller thel...@ctypes.org wrote:
Is there a solution to this? I've seen that the wheel tool can convert
bdist_wininst installers into wheels - does this work for the packages
I mentioned above? Do we have to build
I'm reading up and done all those peps:
425 - compaibility tags
426 - metadata 2.0
427 - wheel binary format 1.0
440 - version identification and dependency specifications
and trying to make sense from them. Well, they make sense to me,
but to what do they apply?
Example: I can now build,
Am 23.01.2014 19:52, schrieb Ralf Gommers:
On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
oscar.j.benja...@gmail.com mailto:oscar.j.benja...@gmail.com wrote:
On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
The official numpy installer uses some complex magic to
Are the specifications in the PEPs above implemented somewhere
or are they only 'specifications'?
The Packaging User Guide is maintaining a summary of the relevant PEPs
that gives a brief description of the user impact and implementation
(i.e. whether projects are actually implementing
Am 06.12.2013 13:22, schrieb Nick Coghlan:
On 6 December 2013 17:10, Thomas Heller thel...@ctypes.org wrote:
Am 06.12.2013 06:47, schrieb Nick Coghlan:
Hmm, I just had an idea for how to do the runtime selection thing. It
actually shouldn't be that hard, so long as the numpy folks are OK
Am 06.12.2013 06:47, schrieb Nick Coghlan:
On 6 December 2013 11:52, Donald Stufft don...@stufft.io wrote:
On Dec 5, 2013, at 8:48 PM, Chris Barker - NOAA Federal chris.bar...@noaa.gov
wrote:
What would really be best is run-time selection of the appropriate lib
-- it would solve this
Am 04.12.2013 11:41, schrieb Oscar Benjamin:
On 4 December 2013 07:40, Ralf Gommers ralf.gomm...@gmail.com wrote:
How do I package those three builds into wheels and get the right one
installed by ``pip install numpy``?
This was discussed previously on this list:
Am 03.12.2013 09:56, schrieb Paul Moore:
The scripts argument is generally considered obsolete - tools like
pip will not generate executable wrappers for scripts specified like
this, which means that they will not work properly on Windows.
The Python documentation does not mention this -
Am 03.12.2013 09:56, schrieb Paul Moore:
The scripts argument is generally considered obsolete - tools like
pip will not generate executable wrappers for scripts specified like
this, which means that they will not work properly on Windows.
Maybe pip (or bdist_wheel ?) should emit a Warning or
Am 16.11.2013 21:15, schrieb Paul Moore:
On 16 November 2013 17:59, Thomas Heller thel...@ctypes.org wrote:
What is the preferred format to distribute Python-3 libraries (for Windows)
nowadays: wininst, egg, ...?
Wheel is the format of the future.
pip install will only use wheels (recent
What is the preferred format to distribute Python-3 libraries (for
Windows) nowadays: wininst, egg, ...?
It has been a long time that I have released something.
Thanks,
Thomas
___
Distutils-SIG maillist - Distutils-SIG@python.org
Am 20.08.2013 19:39, schrieb PJ Eby:
I thought that at one point you (Thomas) had come up with a way to
load modules into memory from a zipfile without needing to extract
them. Was that you? If so, how did that work out?
To give a definite answer, after thinking it over:
It works, for quite
Back from holidays, I read this very interesting discussion...
Am 14.08.2013 16:33, schrieb Nick Coghlan:
Aside from the lack of embedded C extension support (which could
likely be fixed if zipimport was migrated to Python code for 3.5),
...but I don't understand what you mean by this. Can
Am 20.08.2013 15:42, schrieb Nick Coghlan:
Importing C extensions requires extracting them to a temp directory and
loading them from there. Trivial in Python, a pain in C. zipimport is
currently still written in C.
So what - zipimport is a builtin module (on Windows at least).
Am 20.08.2013 18:22, schrieb Nick Coghlan:
On 20 Aug 2013 09:18, Thomas Heller thel...@ctypes.org
mailto:thel...@ctypes.org wrote:
Am 20.08.2013 15:42, schrieb Nick Coghlan:
Importing C extensions requires extracting them to a temp directory and
loading them from there. Trivial
Am 20.08.2013 19:39, schrieb PJ Eby:
On Tue, Aug 20, 2013 at 12:39 PM, Thomas Heller thel...@ctypes.org wrote:
Ok, now I understand. But the zipfile could contain a loader-module
for each extension which does something like this (this example extracts
and loads 'bz2.pyd'):
...
(py2exe
Am 15.07.2013 19:26, schrieb Donald Stufft:
Maybe this is a crazy idea, but would a windows only extension work?
.pye(executable) Then just associate .pye with the launcher. Python
won't see .pye as importable so there's no shadow issues.
pip.bat?
Thomas
Am 17.07.2013 15:33, schrieb Paul Moore:
On 17 July 2013 14:13, Thomas Heller thel...@ctypes.org
mailto:thel...@ctypes.org wrote:
Am 15.07.2013 19:26, schrieb Donald Stufft:
Maybe this is a crazy idea, but would a windows only extension work?
.pye(executable) Then just
Am 28.03.2013 17:42, schrieb Paul Moore:
On 28 March 2013 16:02, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Return this directory. Note that the caller is responsible for
deleting this directory and its contents, which might not be
possible - e.g. in Windows, if a shared
pkgutil is somehow connected to setuptools, so I assume this
is the right place to ask this question.
I'm exploring pkgutil.extend_path(), together with a pkg-file
somewhere on my PYTHONPATH.
I am wondering if it is somehow possible to interpret relative
pathnames in the pkg-file relative to the
Tres Seaver schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Moore wrote:
2009/4/9 Lennart Regebro rege...@gmail.com:
2009/4/9 Paul Moore p.f.mo...@gmail.com:
Don't they? I have to admit that I'm baffled by how the features in
setuptools/eggs/easy_install all hang together.
Ian Bicking schrieb:
On Thu, Jan 29, 2009 at 6:49 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Next, (in a second step) I was wondering if a uninstall registery
could not be a good thing to have,
to store a record of the installed files so there's no need to keep
the source for
Eli Bendersky schrieb:
Hello,
I've always assumed that py2exe uses modulefinder (or rather a
self-written version thereof) to find the modules used by the packaged
application. However, I see that py2exe manages to find things that
modulefinder doesn't find, such as DLLs. For example, when
Martin v. Löwis schrieb:
I'd like to propose we delete Lib/Distutils/command/wininst-9.0.exe, and
enable the building of that project by default in the standard build process
(and I'll setup the x64 build of the executable similarly).
There are two issues here:
a) how does the binary get
Sylvain Taverne schrieb:
Hi,
Is it possible to execute the installer generate with the command :
python setup.py bdist_wininst
In a quiet mode ?
Thank's
No.
Thomas
___
Distutils-SIG maillist - Distutils-SIG@python.org
Mark Hammond schrieb:
The pywin32 extensions require (well, prefer) administrative access during
installation - certain files are copied to the System32 directory and the
registry at HKEY_LOCAL_MACHINE is written to. Also, if I understand
correctly, if Python happened to be installed into
Mowry, Peter schrieb:
You cannot use MSVC8 anyway because it links with the wrong C runtime library;
except if you compile thw whole Python with it.
I did some web searching and read that I can:
os.environ['DISTUTILS_USE_SDK'] = 1
os.environ['MSSdk'] = 1
Well, easy_install makes it snap to install packages that I may or may
not use. Nothing is easier than to 'easy_install something-recently-announced',
even if I never will use it (after a preliminary look). Often I forget to
uninstall the packages again, or promise to do that later. Disk space is
The more I manage the third-party packages I have installed with easy_install,
the more I like that I never have to fiddle around in the file system. (Except
when I want to free the space that a no-longer needed package consumes,
easy_install -m package-name works fine).
However (since I'm
Venkat Bommakanti schrieb:
Hi folks,
I'd like to know if there is a source egg of ctypes
(for Python 2.4.x) that can be built and deployed via
setuptools...
I need to be able to cross compile ctypes from an
i686Linux box targeting both i686 and ppc Linux's. I'd
like to deploy it with a
Paul Pogonyshev schrieb:
Thomas Heller wrote:
Paul Pogonyshev schrieb:
Hi,
Distutils create dynamic library for a C extension in `build/...'
directory. This makes it impossible to run program without
installing it, which I find very important for developing. Ideally,
process
Paul Pogonyshev schrieb:
Hi,
Distutils create dynamic library for a C extension in `build/...'
directory. This makes it impossible to run program without
installing it, which I find very important for developing. Ideally,
process should look like this:
edit Python code - test
Phillip J. Eby schrieb:
For my education: what are old-style scripts?
A script specified in the 'scripts' option to setup(), as opposed to via
entry_points.
Now, what I just realized when I typed that answer above, is that normally
Python scripts specified in setup() would be installed
Bob Ippolito schrieb:
On 11/8/06, Thomas Heller [EMAIL PROTECTED] wrote:
In the easy_install docs is mentioned (at the end):
Added subversion download support for svn: and svn+ URLs, as well as
automatic recognition of HTTP subversion URLs
How does this work? Is it possible to install
On 11/9/06, Thomas Heller [EMAIL PROTECTED] wrote:
It looks like all the information that is needed to implement the above
two features - is there a reason why this isn't implemented?
Paul Moore schrieb:
I believe it's simply a lack of time. Phillip has talked about
implementing a nest
In the easy_install docs is mentioned (at the end):
Added subversion download support for svn: and svn+ URLs, as well as
automatic recognition of HTTP subversion URLs
How does this work? Is it possible to install a package from an svn
repository, when the repository resides
(read-only) at
Bernhard Herzog [EMAIL PROTECTED] writes:
M.-A. Lemburg [EMAIL PROTECTED] writes:
What do you have in mind - a bdist_wininst lookalike for
Python packages, built with inno?
Yes. One that creates an Inno setup file and then compiles
everything into an installer using the Inno, but
installer for Windows
Included in py2exe by Thomas Heller:
http://starship.python.net/crew/theller/py2exe/
That's not really a distutils distribution format, it is a sample setup
script which builds an exe file plus the needed support files with
py2exe, and then builds a Windows installer
Kevin Dangoor [EMAIL PROTECTED] writes:
Phillip suggested that this would be a good addition to the py2exe
wiki, but it appears that the py2exe wiki is closed off. This message
is my recipe for using py2exe (and py2app with basically the same
code) with eggs.
The wiki should be open once you
Trent Mick [EMAIL PROTECTED] writes:
[Phillip J. Eby wrote]
With Perl and Ruby, for example, scripts from a
3rd party package will be installed next to the main interpreter binary
(i.e. on the PATH) on all platforms. Would having setuptools (and
changing distutils) to install scripts next
Paul Moore [EMAIL PROTECTED] writes:
On 9/17/05, Phillip J. Eby [EMAIL PROTECTED] wrote:
However, after reflection, I think now that -m probably only really makes
sense for stdlib modules, since projects using setuptools can now get all
the benefits of -m without any of the drawbacks, without
I'm slowly getting tired maintaining py2exe. It is far from perfect,
although it has interesting features (I would say).
The problem, apart from the work, is that it is good enough for me - I
can do everything that I need with it. But I assume I use far less
libaries than other Python
Trent Mick [EMAIL PROTECTED] writes:
I haven't yet played with setuptools/eggs/etc. so my comments might be
ignorant.
[Phillip J. Eby wrote]
Then EasyInstall could create a 'unittest' script with a #! line on
Unix-like OSes, and a 'unittest.py', 'unittest.bat', or 'unittest.exe' on
Seems I was late to try out setuptools. Fantastic package, is my first
impression. But I have still a lot to read and tryout.
But here is a first question: The 'test' command runs 'build_ext -i' and
then the tests. Usually, I test my packages with several Python
versions.
Now, the problem is
Phillip J. Eby [EMAIL PROTECTED] writes:
At 07:08 PM 8/18/2005 +0200, Thomas Heller wrote:
Seems I was late to try out setuptools. Fantastic package, is my first
impression. But I have still a lot to read and tryout.
But here is a first question: The 'test' command runs 'build_ext -i
Barry Warsaw [EMAIL PROTECTED] writes:
On Thu, 2005-06-30 at 10:01, Paul Moore wrote:
Have you tried
python setup.py build --build-base=whatever install
?
I chain the commands like this to switch compilers on Windows (build
--compiler=mingw32 bdist_wininst) and it works fine for
54 matches
Mail list logo
