On 14 April 2015 at 06:37, David Cournapeau courn...@gmail.com wrote:
pywin32 is one of the most used package in the python ecosystem, and its
post install script is not trivial.
And yet pywin32's postinstall script is completely virtualenv-hostile.
It registers start menu entries (not
Tl;dr: I woud like to change PEP-440 to remove the stigmata around dev
versions that come between pre-releases and releases.
The basic scenario here is developers and CD deployers building
versions from VCS of arbitrary commits. So we need to be able to
deliver strictly increasing version
On 14 April 2015 at 10:04, Robert Collins robe...@robertcollins.net wrote:
The basic scenario here is developers and CD deployers building
versions from VCS of arbitrary commits. So we need to be able to
deliver strictly increasing version numbers, automatically, without
interfering with
That's exactly what I would like to do. Then
distribution-1.0.data/sysconfdir/file in a wheel would install into
/etc/file in the default scheme, but would probably really wind up in
$VIRTUAL_ENV/etc/... for most of us web developers.
IIRC extra package-1.0-data/* directories in wheel are
On Mon, Apr 13, 2015 at 10:13 PM Donald Stufft don...@stufft.io wrote:
On Apr 13, 2015, at 8:57 PM, Ben Finney ben+pyt...@benfinney.id.au
wrote:
Nick Coghlan ncogh...@gmail.com writes:
On 11 Apr 2015 12:22, Alexander Walters tritium-l...@sdamon.com
wrote:
Is the package index
On Tue, Apr 14, 2015 at 8:41 AM, Nick Coghlan ncogh...@gmail.com wrote:
The main two language independent solutions I've identified for this
general user level package management problem in the Fedora
Environments Stacks context
(
On 14 April 2015 at 17:10, Chris Barker chris.bar...@noaa.gov wrote:
If there’s a plugin that understands this extension
installed, let it do something before you actually move the files into
place”. This let’s Wheels themselves still be declarative and moves the
responsibility of
On 14 April 2015 at 11:16, Brett Cannon br...@python.org wrote:
I agree. Even something as simple as a boolean that triggers a banner
saying this project is looking for a new maintainer would be useful both
from the perspective of project owners who want to move on or from the
perspective of
On 13 April 2015 at 12:56, Chris Barker chris.bar...@noaa.gov wrote:
Which brings me back to the question: should the python tools (i.e. wheel)
be extended to support more use-cases, specifically non-python dependencies?
Or do we just figure that that's a problem better solved by projects with
On 13 April 2015 at 22:29, Donald Stufft don...@stufft.io wrote:
So a possible way for this to work is in a PEP 426 world, simply define
a twisted.plugins extension that says, in a declarative way, “hey when
you install this Wheel, if there’s a plugin that understands this extension
installed,
If there’s a plugin that understands this extension
installed, let it do something before you actually move the files into
place”. This let’s Wheels themselves still be declarative and moves the
responsibility of implementing these bits into their own PyPI projects
that can be versioned
On 13 April 2015 at 02:24, Thomas Güttler guettl...@thomas-guettler.de wrote:
Hi,
somehow I feel bored if I read PEP 426.
https://www.python.org/dev/peps/pep-0426/
If anyone didn't find the complexities of real world software
distribution tedious, frustrating and often mindnumbingly dull, I'd
On 14 April 2015 at 11:19, Trishank Karthik Kuppusamy trish...@nyu.edu
wrote:
On 14 April 2015 at 11:16, Brett Cannon br...@python.org wrote:
I agree. Even something as simple as a boolean that triggers a banner
saying this project is looking for a new maintainer would be useful
both
from the
Nick Coghlan ncogh...@gmail.com writes:
Yep, Guido's keynote was the genesis of the thread.
I can't find it online, can you give a URL so we can see the talk?
Past suggestions for social features have related to providing users
with a standard way to reach maintainers and each other, and I'd
On 14 April 2015 at 23:31, Joost Molenaar j.j.molen...@gmail.com wrote:
On 14 April 2015 at 10:04, Robert Collins robe...@robertcollins.net wrote:
The basic scenario here is developers and CD deployers building
versions from VCS of arbitrary commits. So we need to be able to
deliver strictly
On Tue, Apr 14, 2015 at 4:19 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 14 April 2015 at 22:02, Chris Barker chris.bar...@noaa.gov wrote:
Personally, I'm not a fan of auto-installing, so I'd hope for
something more like pip would fail to install if a required extension
were missing. The
On Tue, Apr 14, 2015 at 9:27 AM, Daniel Holth dho...@gmail.com wrote:
That's exactly what I would like to do. Then
distribution-1.0.data/sysconfdir/file in a wheel would install into
/etc/file in the default scheme, but would probably really wind up in
$VIRTUAL_ENV/etc/... for most of us web
Just implement it. You could also try editing wheel's own proof of
concept installer.
https://bitbucket.org/pypa/wheel/src/tip/wheel/install.py?at=default#cl-246
On Tue, Apr 14, 2015 at 3:20 PM, David Cournapeau courn...@gmail.com wrote:
On Tue, Apr 14, 2015 at 9:27 AM, Daniel Holth
On 14 Apr 2015 09:28, Daniel Holth dho...@gmail.com wrote:
That's exactly what I would like to do. Then
distribution-1.0.data/sysconfdir/file in a wheel would install into
/etc/file in the default scheme, but would probably really wind up in
$VIRTUAL_ENV/etc/... for most of us web developers.
Trishank Karthik Kuppusamy trish...@nyu.edu writes:
Yeah, I think Guido said something to this effect in his keynote.
Apparently I'm missing that context, then. The original post didn't help
me understand why this proposal is significantly different from past
“add a bunch of social to PyPI”
Hi,
I am splitting up the previous thread into one thread / proposal to focus
the discussion.
Assuming the basis of this proposal does not sound too horrible, I would
make a proof of concept in a pip branch, so that we can flush out the
details and then write an actual spec (I guess an updated
On 14 April 2015 at 22:02, Chris Barker chris.bar...@noaa.gov wrote:
- pip auto-installs it (if not already there) when the user goes to install
the wheel.
Personally, I'm not a fan of auto-installing, so I'd hope for
something more like pip would fail to install if a required extension
were
On Tue, Apr 14, 2015 at 9:46 AM, Paul Moore p.f.mo...@gmail.com wrote:
Could an extension be -- run this arbitrary Python script ?
The main point (as I see it) of an extension is that it's
distributed independently of the packages that use it. So you get to
decide to use an extension (and
On Apr 14, 2015, at 6:46 PM, Ben Finney ben+pyt...@benfinney.id.au wrote:
Trishank Karthik Kuppusamy trish...@nyu.edu writes:
Yeah, I think Guido said something to this effect in his keynote.
Apparently I'm missing that context, then. The original post didn't help
me understand why
24 matches
Mail list logo
