On 30 January 2014 05:33, Evgeny Sazhin eug...@sazhin.us wrote:
Eh, I think both 1 and 3 are things that are possibly reasonable to happen and
they are both things that I've contemplated as things to bring forward in
using xz as an alternative compression format. Even if #1 would need a major
On Thu, 30/1/14, Paul Moore p.f.mo...@gmail.com wrote:
This is the biggest concern I see with promoting wheels
being directly importable via zipimport (I say promoting and
not specifying deliberately, but I don't want to get back into
the process
On 30 January 2014 09:45, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
So much heat over process, but so little light over exactly why
*appropriately designed* software deployed in wheels shouldn't be
importable.
Good point.
In my view, *appropriately designed* software is fine, and a metadata
On 30 Jan 2014 15:27, Donald Stufft don...@stufft.io wrote:
I can't believe folks are unable to differentiate between the difference
of
It's possible to do so because we didn't actively attempt to prevent it
and
This is a documented goal of the format and thus must be considered as
part of
the
My one technical issue is with going beyond zipimport
behaviour to the point of extracting DLLs to the filesystem.
I remain -1 on that feature, and I believe I have explained why I think
there are issues (and why I think that any solution should be part of
zipimport and not added on in
On 30 January 2014 11:57, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
ISTM the reason why it can't
go in there just yet is also the reason why one might have some reservations
about the feature: binary compatibility
Sorry, I didn't comment on this point. To me, binary compatibility is
*not* the
On Jan 30, 2014, at 9:30 AM, Donald Stufft don...@stufft.io wrote:
On Jan 30, 2014, at 6:43 AM, Nick Coghlan ncogh...@gmail.com wrote:
On 30 Jan 2014 15:27, Donald Stufft don...@stufft.io wrote:
I can't believe folks are unable to differentiate between the difference of
It's possible
On 30 January 2014 15:03, Donald Stufft don...@stufft.io wrote:
For those following along at home who have no interest in supporting zipped
Wheels who want to disclaim support for it, here's how you do zip_safe=False
for Wheels: https://gist.github.com/dstufft/8710270.
Note that this will also
On Jan 30, 2014, at 10:12 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 30 January 2014 15:03, Donald Stufft don...@stufft.io wrote:
For those following along at home who have no interest in supporting zipped
Wheels who want to disclaim support for it, here's how you do zip_safe=False
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/2014 10:23 AM, Donald Stufft wrote:
On Jan 30, 2014, at 10:12 AM, Paul Moore p.f.mo...@gmail.com
wrote:
On 30 January 2014 15:03, Donald Stufft don...@stufft.io
wrote:
For those following along at home who have no interest in
I see you've noticed wheel was released in an imperfect state.
Let's add a Zip-Safe flag to the WHEEL file, values of true and
false same as Root-Is-Purelib.
Daniel
On Thu, Jan 30, 2014 at 10:44 AM, Eric V. Smith e...@trueblade.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On
Just an FYI, I've begun compiling notes and plan on proposing PEPs that will be
aimed at supplanting PEP 425 and PEP 427 with the goal of nailing down
undefined behavior, including missing functionality, and removing misfeatures.
On Jan 30, 2014, at 10:56 AM, Daniel Holth dho...@gmail.com wrote:
On Thu, 30/1/14, Eric V. Smith e...@trueblade.com wrote:
The flag really needs to convey 2 meanings:
- - There are some C extensions here that can't be loaded
unless they live on a real filesystem path.
- - There is some code (maybe in
On Thu, Jan 30, 2014 at 3:09 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 30 January 2014 05:33, Evgeny Sazhin eug...@sazhin.us wrote:
Eh, I think both 1 and 3 are things that are possibly reasonable to happen
and
they are both things that I've contemplated as things to bring forward in
using xz
On Thu, Jan 30, 2014 at 11:59 AM, Donald Stufft don...@stufft.io wrote:
On Jan 30, 2014, at 11:33 AM, Evgeny Sazhin eug...@sazhin.us wrote:
On Thu, Jan 30, 2014 at 3:09 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 30 January 2014 05:33, Evgeny Sazhin eug...@sazhin.us wrote:
Eh, I think both
On 30 January 2014 16:33, Evgeny Sazhin eug...@sazhin.us wrote:
I don't have good
references or pointers to good Python development or deployment
practices, but you may want to ask around on python-list.
And that is my biggest concern (deployment). I believe these questions
should be
On Thu, Jan 30, 2014 at 12:56 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 30 January 2014 16:33, Evgeny Sazhin eug...@sazhin.us wrote:
I don't have good
references or pointers to good Python development or deployment
practices, but you may want to ask around on python-list.
And that is my
One thing that might be useful would be to develop the unpacked
wheel which is currently undefined but would be deliberately
identical to a site-packages with just one wheel extracted into it.
You wouldn't have to argue or worry about the zip issue.
I like the way npm puts everything into a
On Thu, Jan 30, 2014 at 1:24 PM, Daniel Holth dho...@gmail.com wrote:
One thing that might be useful would be to develop the unpacked
wheel which is currently undefined but would be deliberately
identical to a site-packages with just one wheel extracted into it.
You wouldn't have to argue or
On 30 Jan 2014, at 17:27, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
On Thu, 30/1/14, Eric V. Smith e...@trueblade.com wrote:
The flag really needs to convey 2 meanings:
- - There are some C extensions here that can't be loaded
unless
On Thu, Jan 30, 2014 at 2:15 PM, Evgeny Sazhin eug...@sazhin.us wrote:
On Thu, Jan 30, 2014 at 1:24 PM, Daniel Holth dho...@gmail.com wrote:
One thing that might be useful would be to develop the unpacked
wheel which is currently undefined but would be deliberately
identical to a site-packages
On Thu, Jan 30, 2014 at 2:32 PM, Daniel Holth dho...@gmail.com wrote:
On Thu, Jan 30, 2014 at 2:15 PM, Evgeny Sazhin eug...@sazhin.us wrote:
On Thu, Jan 30, 2014 at 1:24 PM, Daniel Holth dho...@gmail.com wrote:
One thing that might be useful would be to develop the unpacked
wheel which is
On Thu, Jan 30, 2014 at 12:46 PM, Evgeny Sazhin eug...@sazhin.us wrote:
On Thu, Jan 30, 2014 at 11:59 AM, Donald Stufft don...@stufft.io wrote:
On Jan 30, 2014, at 11:33 AM, Evgeny Sazhin eug...@sazhin.us wrote:
On Thu, Jan 30, 2014 at 3:09 AM, Paul Moore p.f.mo...@gmail.com
wrote:
On
On Thu, Jan 30, 2014 at 2:52 PM, Brett Cannon br...@python.org wrote:
still far from seeing good reasoning. Please, correct me, but so far i
saw 2:
1. It is impossible to load C extensions
2. Error handling is bad
None of these reasons seems to be good enough to lead to a conclusion
Wow, it really can install from a directory-named-like-a-wheel with
the --no-index flag passed. I'm sad to say that is totally
unintentional, but bizarrely interesting.
On Thu, Jan 30, 2014 at 2:52 PM, Evgeny Sazhin eug...@sazhin.us wrote:
On Thu, Jan 30, 2014 at 2:32 PM, Daniel Holth
On Thu, 30/1/14, Daniel Holth dho...@gmail.com wrote:
Wow, it really can install from a directory-named-like-a-wheel with
the --no-index flag passed. I'm sad to say that is totally unintentional,
but bizarrely interesting.
What, *more*
I have clearly done a bad job so far of explaining the clarification in PEP
427, so here's a new attempt that relies solely on the PEP text and the way
the import system works, rather than the fact that the discussions around
the PEP show that the import system compatibility was a deliberate
On Jan 29, 2014, at 5:24 PM, Nick Coghlan ncogh...@gmail.com wrote:
I have clearly done a bad job so far of explaining the clarification in PEP
427, so here's a new attempt that relies solely on the PEP text and the way
the import system works, rather than the fact that the discussions
But that's what I'm saying, there are only three ways to break this
behaviour:
1. Changing the wheel format in such a way that we drop support for being
able to install simple wheel files without a specialised installer
2. Break zipimport itself to explicitly disallow wheel files
3. Switch to a
On Jan 29, 2014, at 5:59 PM, Nick Coghlan ncogh...@gmail.com wrote:
But that's what I'm saying, there are only three ways to break this behaviour:
1. Changing the wheel format in such a way that we drop support for being
able to install simple wheel files without a specialised installer
On Jan 29, 2014, at 2:59 PM, Nick Coghlan ncogh...@gmail.com wrote:
But that's what I'm saying, there are only three ways to break this behaviour:
1. Changing the wheel format in such a way that we drop support for being
able to install simple wheel files without a specialised installer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/2014 06:55 PM, Noah Kantrowitz wrote:
If you are going to document this, and it is not going to be
explicitly supported by the spec (it isn't), the _only_ logical thing
is to document that this is undefined behavior and while it works
On Jan 29, 2014, at 8:50 PM, Tres Seaver tsea...@palladion.com wrote:
Signed PGP part
On 01/29/2014 06:55 PM, Noah Kantrowitz wrote:
If you are going to document this, and it is not going to be
explicitly supported by the spec (it isn't), the _only_ logical thing
is to document that
On Jan 29, 2014, at 11:50 PM, Tres Seaver tsea...@palladion.com wrote:
Signed PGP part
On 01/29/2014 06:55 PM, Noah Kantrowitz wrote:
If you are going to document this, and it is not going to be
explicitly supported by the spec (it isn't), the _only_ logical thing
is to document that
Eh, I think both 1 and 3 are things that are possibly reasonable to happen and
they are both things that I've contemplated as things to bring forward in
using xz as an alternative compression format. Even if #1 would need a major
revision of Wheel to happen adding official support for zip import
On Jan 29, 2014, at 11:50 PM, Tres Seaver tsea...@palladion.com wrote:
Signed PGP part
On 01/29/2014 06:55 PM, Noah Kantrowitz wrote:
If you are going to document this, and it is not going to be
explicitly supported by the spec (it isn't), the _only_ logical thing
is to document that
On Jan 30, 2014, at 12:33 AM, Evgeny Sazhin eug...@sazhin.us wrote:
Eh, I think both 1 and 3 are things that are possibly reasonable to happen
and
they are both things that I've contemplated as things to bring forward in
using xz as an alternative compression format. Even if #1 would need a
37 matches
Mail list logo
