In the binary dependency management threads, Daniel pointed out that
in all currently defined sysconfig schemes, the data directory will
end up pointing to the target installation directory. The data name
in the scheme doesn't actually mean this is a data file, it means
this has no defined
On Thursday, December 05, 2013 06:37:39 PM Michael Jansen wrote:
On Tuesday, December 03, 2013 12:33:22 PM Michael Jansen wrote:
Changes to distutils itself are fairly pointless, since the earliest
possible date for publication of any such changes is now as part of
Python 3.5 in 2015.
On 7 December 2013 08:19, Nick Coghlan ncogh...@gmail.com wrote:
That means that you can ship relatively arbitrary software in a wheel
file by dumping it in {distribution}-{version}.data/data/path, and
then installing it to the appropriate target location (e.g. if you use
FHS paths inside the
On Saturday, December 07, 2013 06:19:42 PM Nick Coghlan wrote:
In the binary dependency management threads, Daniel pointed out that
in all currently defined sysconfig schemes, the data directory will
end up pointing to the target installation directory. The data name
in the scheme doesn't
On 7 December 2013 10:12, Michael Jansen i...@michael-jansen.biz wrote:
I made a proof of concept implementation (not ready to be merged) here
No one interested in that? Got no answer from the maintainers too.
Personally, I'm against the idea on principle, because the bin/sbin
distinction is
On Saturday, December 07, 2013 10:26:15 AM Paul Moore wrote:
On 7 December 2013 08:19, Nick Coghlan ncogh...@gmail.com wrote:
That means that you can ship relatively arbitrary software in a wheel
file by dumping it in {distribution}-{version}.data/data/path, and
then installing it to the
On Saturday, December 07, 2013 10:56:16 AM Paul Moore wrote:
On 7 December 2013 10:12, Michael Jansen i...@michael-jansen.biz wrote:
I made a proof of concept implementation (not ready to be merged) here
No one interested in that? Got no answer from the maintainers too.
Personally, I'm
On 7 December 2013 11:10, Michael Jansen i...@michael-jansen.biz wrote:
I guess we agree here. But people already do that because they have no other
choice. Nick only wants to document the way it works better. Many people
already figured this out and use it anyway.
I believe it's an attractive
On 7 December 2013 11:14, Michael Jansen i...@michael-jansen.biz wrote:
And then setting those variables in cross platform compatible ways.
Well, OK, but there may not *be* a cross platform compatible answer
- we could set sbin to the same as bin on Windows, but www is probably
inside the Apache
I really don't have all the answers here, but...
On 7 December 2013 12:30, Michael Jansen i...@michael-jansen.biz wrote:
So you consider anything that has parts that need to be installed into/under
a web server as not windows compatible?
Not at all. If you're talking about documents, what's to
On Saturday, December 07, 2013 01:16:27 PM Paul Moore wrote:
I really don't have all the answers here, but...
On 7 December 2013 12:30, Michael Jansen i...@michael-jansen.biz wrote:
So you consider anything that has parts that need to be installed
into/under a web server as not windows
On 7 December 2013 13:45, Michael Jansen i...@michael-jansen.biz wrote:
Anyway. You are at least willing to discuss with me. So thanks.
No problem! I hope I wasn't too discouraging - I get the impression
that I was :-(
My problem is that I don't know the answers on Windows, I only really
know
As part of the docs clarification, I was planning to point out that such
layouts are almost always platform (and even distro) specific. That's still
a valid use case for sdist and wheel, though, so it makes sense to me to
document it properly.
My other related question is whether it's possible to
FWIW, tackling FHS compliance is one of the things I have in mind as being
suitable for a metadata 2.0 extension.
Because Mac OS X and Windows just bundle (almost) everything into the
application directory, FHS concepts simply don't map properly, so the
current best FHS compliant solution is to
On Saturday, December 07, 2013 03:15:15 PM Paul Moore wrote:
On 7 December 2013 13:45, Michael Jansen i...@michael-jansen.biz wrote:
I can understand your situation, but please don't give up! The
packaging community definitely needs people willing to help work on
these issues. But it's much
On 7 December 2013 16:56, Michael Jansen i...@michael-jansen.biz wrote:
A windows developer should not care about the difference. Both end up in the
same directory. [...] will one day get a bug report/patch from a unix user
OK, cool. That makes sense.
Paul
The PyPA is pleased to announce the Setuptools 2.0 release.
This backward-incompatible release drops support for Python 2.4 and Python 2.5,
but is otherwise compatible with 1.x releases.
The 1.x series will continue to be supported for bug and security fixes for the
foreseeable future.
As part of the docs clarification, I was planning to point out that such
layouts are almost always platform (and even distro) specific. That's still
a valid use case for sdist and wheel, though, so it makes sense to me to
document it properly.
My other related question is whether it's
actually, bdist_wheel doesn't handle absolute paths in the data_files
keyword like standard setuptools installs do, which honor it as absolute
(which seems to match the examples in the distutils docs)
when using absolute paths, the data ends up in the packaged wheel at the
top level (not in the
https://bitbucket.org/dholth/wheel/issue/92/bdist_wheel-makes-absolute-data_files
On Sat, Dec 7, 2013 at 1:32 PM, Marcus Smith qwc...@gmail.com wrote:
actually, bdist_wheel doesn't handle absolute paths in the data_files
keyword like standard setuptools installs do, which honor it as absolute
On 7 December 2013 21:32, Marcus Smith qwc...@gmail.com wrote:
actually, bdist_wheel doesn't handle absolute paths in the data_files
keyword like standard setuptools installs do, which honor it as absolute
(which seems to match the examples in the distutils docs)
when using absolute paths, the
Just a note here:
the wxWidgets (and thus wxPython, natch) project has a wxStandardPaths
object:
http://docs.wxwidgets.org/trunk/classwx_standard_paths.html
It provides a cross platform way to get, well, the standard paths an
application might need:
GetAppDocumentsDir ()
GetConfigDir ()
Nick Coghlan ncoghlan at gmail.com writes:
Hi Kanaan,
I believe twine (https://pypi.python.org/pypi/twine/) should work as
the independent upload utility that you're looking for.
Cheers,
Nick.
That's perfect, thanks. (Also thanks to Daniel Holth who replied off-list.)
Another great
On 8 December 2013 08:22, Paul Moore p.f.mo...@gmail.com wrote:
On 7 December 2013 21:32, Marcus Smith qwc...@gmail.com wrote:
actually, bdist_wheel doesn't handle absolute paths in the data_files
keyword like standard setuptools installs do, which honor it as absolute
(which seems to match
24 matches
Mail list logo
