On 16 April 2015 at 17:42, Wes Turner wrote:
>
> On Apr 14, 2015 7:15 PM, "Nick Coghlan" wrote:
>>
>> [...]
>>
>> The perception that open source software is provided by magic internet
>> pixies that don't need to eat (or at the very least to be thanked for the
>> time their generosity has saved
On 16 Apr 2015 14:34, "Paul Moore" wrote:
>
> By the way. I just did a check through PEPs 426 and 459. Neither one
> currently defines a "postinstall script" metadata item or extension,
> which is interesting given that this discussion started from the
> question of how postinstall actions would b
On 16 Apr 2015 03:08, "Paul Moore" wrote:
>
> Just to expand on another point in my mail - I'd like *anyone* to
> provide an example of a genuine use case for something they think
> should be a "required" installer extension. I'm not sure such a thing
> actually exists...
The constraints extensio
Okay, I tried to summarize the discussion and most of my thoughts on that
issue. https://github.com/pypa/pip/issues/988
I'll post anything further I have to say there. I hope to get a student to
measure the extent of the problem...
Thanks,
Justin
On Wed, Apr 15, 2015 at 2:44 PM, Jeremy Stanley
As already mentioned in this thread, most of the postinstall stuff is
needed only for a subset of users - mainly those who want to write COM
objects or Windows Services (and also people who want the shortcuts etc).
pywin32 itself should be close to "portable" - eg, "setup.py install"
doesn't r
On Apr 14, 2015 7:15 PM, "Nick Coghlan" wrote:
>
> [...]
>
> The perception that open source software is provided by magic internet
pixies that don't need to eat (or at the very least to be thanked for the
time their generosity has saved us)
https://en.wikipedia.org/wiki/Business_models_for_open-
On Apr 14, 2015 7:15 PM, "Nick Coghlan" wrote:
>
> On 14 April 2015 at 11:19, Trishank Karthik Kuppusamy
wrote:
> > On 14 April 2015 at 11:16, Brett Cannon wrote:
> >> I agree. Even something as simple as a boolean that triggers a banner
> >> saying "this project is looking for a new maintainer"
On Thu, Apr 16, 2015 at 9:58 AM, Paul Moore wrote:
> On 16 April 2015 at 14:43, Kevin Horn wrote:
> > Those that want to use pywin32 in a virtualenv (or just without all the
> > system changes) could simply install the wheel (or even an sdist,
> perhaps)
> > from the command line using pip, and
On Tue, Apr 14, 2015 at 8:34 PM Ben Finney
wrote:
> Nick Coghlan 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?
>
https://www.youtube.com/watch?v=G-uKNd5TSBw
>
> > Past suggestions for social features ha
On 16 April 2015 at 17:58, Chris Barker wrote:
> We have the same problem with optional dependencies.
>
> For instance, for iPython to work, you don't need much. but if you want the
> ipython notebook to work, you need tornado, zeromq, who knows what else. But
> people want it to just work -- and
On Wed, Apr 15, 2015 at 2:23 PM, Paul Moore wrote:
> In the PEP, there's a concept of "optional" vs "required" extensions.
> See https://www.python.org/dev/peps/pep-0426/#required-extension-handling.
> This is crucial - I've no problem if a particular extension is used by
> a project, as long as
On 16 April 2015 at 14:43, Kevin Horn wrote:
> Those that want to use pywin32 in a virtualenv (or just without all the
> system changes) could simply install the wheel (or even an sdist, perhaps)
> from the command line using pip, and then perform whatever other steps they
> want manually.
Just a
This seems like a good time to remind everyone that "wheel convert"
can turn bdist_wininst .exe's to wheels. Both formats are designed to
preserve all the distutils file categories. In the future it would be
nice if the bdist_wininst .exe wrapper used wheel instead of its own
format. Then a single
On 16 April 2015 at 11:11, Tim Golden wrote:
> Really, pywin32 is several things: a set of libraries (win32api,
> win32file, etc.); some system-level support for various things (COM
> registration, Service support etc.); and a development/editing
> environment (pythonwin).
That sounds about right
Tim,
As a long time user, I think you're right on the money.
My only concern is how to manage the transition in user experience, as
moving to what you've described (which I totally approve of, if it's
feasible) will be a significant change, and may break user expectations.
I think maybe the best
On 16/04/2015 08:08, Paul Moore wrote:
> On 16 April 2015 at 00:48, Steve Dower wrote:
>> On the Start Menu suggestion, I think that's a horrible idea. Pip is not the
>> system package manager and it shouldn't be changing the system. Unversioned
>> script launchers are in the same category, but ar
[cc-ing Mark H as he indicated he was open to be kept in the loop; also
changed the title to reflect the shift of conversation]
On 16/04/2015 09:21, Paul Moore wrote:
> On 16 April 2015 at 08:30, Tim Golden wrote:
>>> Sorry - I agree it's an awful idea. Older wininst installers such as
>>> the py
On 16 April 2015 at 08:30, Tim Golden wrote:
>> Sorry - I agree it's an awful idea. Older wininst installers such as
>> the pywin32 (and I think the PyQT one) one do this, I wanted to use it
>> as an example of abuse of postinstall scripts that should *not* be
>> perpetuated in any new scheme.
>
>
On 16 April 2015 at 00:48, Steve Dower wrote:
> On the Start Menu suggestion, I think that's a horrible idea. Pip is not the
> system package manager and it shouldn't be changing the system. Unversioned
> script launchers are in the same category, but aren't quite as offensive.
>
> I know it's onl
19 matches
Mail list logo
