[EMAIL PROTECTED] writes:
> I still think it worthwhile to have *some* target in the Makefile
> which depends on altinstall and does the bininstall and maninstall
> steps. Something like "makeprimary"?
How about "install-as-python" or "install-as-default"?
___
On Wed, Mar 5, 2008 at 2:31 PM, <[EMAIL PROTECTED]> wrote:
>
> Guido> I guess I wasn't clear -- I don't want there to be a target that
> Guido> does what install does today. It would be a mistake to use it in
> Guido> 99.99% of cases. IOW
>
> Guido> install = altinstall
>
> The
Guido> I guess I wasn't clear -- I don't want there to be a target that
Guido> does what install does today. It would be a mistake to use it in
Guido> 99.99% of cases. IOW
Guido> install = altinstall
The install target does three things (ignoring Mac framework installs):
a
Oleg Broytmann wrote:
>forceinstall? dangerous-install? damaging-install? (half-wink ;)
burnmybridgesinstall
--
Greg
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.p
On Wed, Mar 5, 2008 at 1:40 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > I guess I wasn't clear -- I don't want there to be a target that does
> > what install does today. It would be a mistake to use it in 99.99% of
> > cases. IOW
> >
> > install = altinstall
>
Guido van Rossum wrote:
> I guess I wasn't clear -- I don't want there to be a target that does
> what install does today. It would be a mistake to use it in 99.99% of
> cases. IOW
>
> install = altinstall
Leaving it up to packagers for the different distributions to decide if
they want to add
On Wed, Mar 05, 2008 at 12:11:50PM -0600, [EMAIL PROTECTED] wrote:
> Guido> Actually I believe the conclusion was that "make install" should
> Guido> be have like "make altinstall". Now that I think about it I
> Guido> believe there should be *no* way to install it as just "python"
>
On Wed, Mar 05, 2008 at 09:39:16AM -0800, Guido van Rossum wrote:
> Actually I believe the conclusion was that "make install" should be
> have like "make altinstall". Now that I think about it I believe there
> should be *no* way to install it as just "python" -- that's just
> encouraging people to
yikes!
skip> If, in the future, the install target does what the altinstall target
does
skip> today, what should the target that does what the install target does
today?
skip> (???, install) = (install, altinstall)
Let me try this again. If, in the future, the install target
On Wed, Mar 5, 2008 at 10:11 AM, <[EMAIL PROTECTED]> wrote:
>
> Guido> Actually I believe the conclusion was that "make install" should
> Guido> be have like "make altinstall". Now that I think about it I
> Guido> believe there should be *no* way to install it as just "python"
> Gu
Guido> Actually I believe the conclusion was that "make install" should
Guido> be have like "make altinstall". Now that I think about it I
Guido> believe there should be *no* way to install it as just "python"
Guido> -- that's just encouraging people to do something dumb.
Well, wh
On Wed, Mar 5, 2008 at 3:31 AM, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 05, 2008 at 11:28:22AM +, Paul Moore wrote:
> > There was a discussion on this list not long ago, under the title
> > "Namespaces are one honking great idea". You might want to look at
> > that. I don't r
On Wed, Mar 5, 2008 at 5:33 AM, Neal Becker <[EMAIL PROTECTED]> wrote:
> It is a bit unfortunate that slicing has a singularity.
>
> samples_to_trim = (some calculation yielding an integer >= 0)
>
>
> trimmed_vector = vector[:-samples_to_trim] if samples_to_trim != 0 else
> vector[:]
>
> A bit unfo
Martijn> "If you install Python 3.x on a system that already uses Python
Martijn> 2.x, we encourage you to use 'make altinstall'. Doing "make
Martijn> install" risks breaking existing scripts until they have been
Martijn> updated to work with Python 3.0."
Of course the same holds
> I guess it might be too late, but has anyone considered:
>
> def func(normal_arg, *, positional_arg, **, keyword_arg):
> pass
Or even that, since it's meaningless to have a positional argument in the
middle:
def func(positional_arg, *, normal_arg, **, keyword_arg):
pass
--
Gustavo N
> Agreed. Now can you come up with a syntax for positional-only
> arguments? So far everybody has failed at that, and there are some use
> cases where it's useful too.
I guess it might be too late, but has anyone considered:
def func(normal_arg, *, positional_arg, **, keyword_arg):
pass
--
Oleg Broytmann wrote:
> On Wed, Mar 05, 2008 at 12:42:39PM +0100, Martijn Faassen wrote:
>> altinstall exists, and it doesn't say what it does.
>
>"make altinstall" installs everything including pythonX.Y binary. "make
> install" does "make altinstall" and then hardlinks pythonX.Y to just
> py
On Wed, Mar 05, 2008 at 12:42:39PM +0100, Martijn Faassen wrote:
> altinstall exists, and it doesn't say what it does.
"make altinstall" installs everything including pythonX.Y binary. "make
install" does "make altinstall" and then hardlinks pythonX.Y to just
python. Running "make altinstall" w
Oleg Broytmann wrote:
> On Wed, Mar 05, 2008 at 11:28:22AM +, Paul Moore wrote:
>> There was a discussion on this list not long ago, under the title
>> "Namespaces are one honking great idea". You might want to look at
>> that. I don't recall any conclusion being reached, though.
>
>AFAIR
Hey,
On Wed, Mar 5, 2008 at 12:28 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> On 05/03/2008, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> > This is quick feedback given my experiences installing Python 3 for the
> > first time. Take it as that, please.
> [...]
> > A quick search on the topic f
It is a bit unfortunate that slicing has a singularity.
samples_to_trim = (some calculation yielding an integer >= 0)
trimmed_vector = vector[:-samples_to_trim] if samples_to_trim != 0 else
vector[:]
A bit unfortunate that the case of samples_to_trim == 0 has to be handled
differently.
I don't
On Wed, Mar 05, 2008 at 11:28:22AM +, Paul Moore wrote:
> There was a discussion on this list not long ago, under the title
> "Namespaces are one honking great idea". You might want to look at
> that. I don't recall any conclusion being reached, though.
AFAIR the conclusion was: use "make a
On 05/03/2008, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> This is quick feedback given my experiences installing Python 3 for the
> first time. Take it as that, please.
[...]
> A quick search on the topic found a discussion about this in '05
> without a conclusion, and the following text in PEP
Hi there,
This is quick feedback given my experiences installing Python 3 for the
first time. Take it as that, please.
I just installed Python 3 into my local installation directory, and
noticed it installs as 'python'. I already had a local Python 2.4
installed which I am actively using, and
24 matches
Mail list logo
