I am more worried about the confusion than Guido is. I agree that this will
remain a toy project. But as someone who trains scientist to use Python and
consults with large companies with large Python 2 codebases, I think the
very existence of a thing called "Python 2.8" will serve as a pretext for
On Dec 10, 2016 10:42 AM, "Wes Turner" wrote:
and this is on purpose, since Python is BSD software which
> anyone can use, modify, fork, etc.
>
So, otherwise everyone who forks for any reason is in violation of the
trademark policy?
The trademark issue has nothing to do with the code copyright
issing a step, there is a
documentation bug, or it depends on which OS X version you are using ?
Thanks,
David
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/ma
> macOS Sierra with SIP which cripples dtrace.
>
On that hint, I tried on OSX 11.1. sw_vers says
ProductName: Mac OS X
ProductVersion: 10.11.6
BuildVersion: 15G1108
And there, the example worked as advertised w/ my build of 3.6.0. I will
try on more versions of OS X in our test lab.
David
certificate, but certification seems to work
Are there any official recommendations for downstream packagers beyond PEP
476 ? Is it "acceptable" for downstream packagers to patch python's default
cert locations ?
David
___
Python-Dev mailing
On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield wrote:
>
>
> > On 30 Jan 2017, at 13:53, David Cournapeau wrote:
> >
> > Are there any official recommendations for downstream packagers beyond
> PEP 476 ? Is it "acceptable" for downstream packagers to pa
On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield wrote:
>
>
> > On 30 Jan 2017, at 13:53, David Cournapeau wrote:
> >
> > Are there any official recommendations for downstream packagers beyond
> PEP 476 ? Is it "acceptable" for downstream packagers to pa
On Mon, Jan 30, 2017 at 9:14 PM, Christian Heimes
wrote:
> On 2017-01-30 22:00, David Cournapeau wrote:
> >
> >
> > On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield > <mailto:c...@lukasa.co.uk>> wrote:
> >
> >
> >
> > > On 30 Jan
On Tue, Jan 31, 2017 at 9:19 AM, Cory Benfield wrote:
>
> On 30 Jan 2017, at 21:00, David Cournapeau wrote:
>
>
>
> On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield wrote:
>
>>
>>
>> > On 30 Jan 2017, at 13:53, David Cournapeau wrote:
>> &
Could we have side-by-side English and whatever translated language? Then
also use some sort of typographic indicator like color to show when the
translation is out of date?
On Feb 26, 2017 6:39 PM, "Rob Cliffe" wrote:
>
>
> On 24/02/2017 12:20, Berker Peksağ wrote:
>
>> On Thu, Feb 23, 2017 at
On Sun, Feb 26, 2017 at 11:30 PM, Nick Coghlan wrote:
> On 27 February 2017 at 14:03, David Mertz wrote:
>
>> Could we have side-by-side English and whatever translated language? Then
>> also use some sort of typographic indicator like color to show when the
>> tr
s and runs on AIX for the
vast majority of users and applications. I don't see the benefit in
dropping support for a platform that functions because it doesn't
fully pass the testsuite.
Thanks, David
On Mon, Apr 3, 2017 at 6:56 AM, Victor Stinner wrote:
> Hi,
>
> We have a "
rs, to questions that came
from out of the blue.
;-)
David Goodger
<http://python.net/~goodger>
> - rst_escape # YMMV
> - $ git-changelog.py -r "release/0.3.14" --hdr= "+"`
>
> On Monday, May 1, 2017, Nick Coghlan wrote:
>>
>> On 1 May 2017
ending on
pyOpenSSL as usual?
I'm still writing 2.7 code every day and would love to see it live a
little longer, but accepting every feature request seems the wrong way
to go - and MemoryBIO is a hard sell as a security enhancement, it's new
fun
I agree with MAL and have also been on the Trademarks Committee for 8-9
years. Protecting an actual Mark like the logo is fine, as painful as it is
to someone's say no to an attractive derived logo. But trying to protect a
look-and-feel is way too far down the path of evil (it's what some
proprieta
This is a side issue, do I don't want to go too long with it. But *NO* we
can't always give permission. The problem isn't how permissive PSF might
like to be in the abstract, but trademark law itself. Trademark is "enforce
it or lose it" ... Even passively allowing dilutive derivatives would cause
On Mon, May 29, 2017 at 07:27:05PM -0700, Guido van Rossum wrote:
> Is the author of that article using non-standard terminology? The article
> doesn't appear to be about __slots__ at all.
They're referred to as slots throughout typeobject.c
___
Python-
ing struct members was to allow
tricks like this:
x86_64-linux-gnu/bits/stat.h
94:# define st_atime st_atim.tv_sec /* Backward compatibility. */
95:# define st_mtime st_mtim.tv_sec
96:# define st_ctime st_ctim.tv_sec
Which is relatively saf
the solution would be compatible with every stable
LTS Linux distribution release that was not shipping the latest and
greatest 2.7.
David
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
ht
with their old environments
without forcing an upgrade to 3.x!)
David
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
by
4.2MB, and Python package security depends on 1k lines of memory-safe
code rather than possibly *the* worst example of security-unconcious C
to come into existence since the birth of our industry. Sounds like a
win to me.
Maybe set a standard rather than blindly foll
elled irritability :/
Apologies for the previous post, it was hardly constructive.
David
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
imacy of async
wrap_socket() (which seems to render this entire conversation moot), if
you still really want to go this route, could ctypes be abused to
provide the missing implementation from the underlying libs? It'd be a
hack, but it would only be necessary during boo
How implausible is it to write out the actual memory image of a loaded
Python process? I.e. on a specific machine, OS, Python version, etc? This
can only be overhead initially, of course, but on subsequent runs it's just
one memory map, which the cheapest possible operation.
E.g.
$ python3.7 --wr
I would guess that Windows users don't tend to run lots of command line
tools where startup time dominates, as *nix users do.
On Fri, Jul 21, 2017 at 3:21 PM, Barry Warsaw wrote:
> On Jul 21, 2017, at 01:25 PM, Nikolaus Rath wrote:
>
> >That is what Emacs does, and it causes them a lot of troubl
This is now looking really good and I can understands it.
One question though. Sometimes creation of a context variable is done with
a name argument, other times not. E.g.
var1 = new_context_var('var1')
var = new_context_var()
The signature is given as:
sys.new_context_var(name: str)
But
Would it be possible/desirable to make the default a unique string value
like a UUID or a stringified counter?
On Aug 26, 2017 9:35 AM, "Yury Selivanov" wrote:
On Sat, Aug 26, 2017 at 12:56 AM, David Mertz wrote:
> This is now looking really good and I can understands it.
Gr
I'm convinced by the new section explaining why a single value is better
than a namespace. Nonetheless, it would feel more "Pythonic" to me to
create a property `ContextVariable.val` whose getter and setter was
`.lookup()` and `.set()` (or maybe `._lookup()` and `._set()`).
Lookup might require a
This sounds like something worthwhile to put on GitHub and PyPI. But it
doesn't seem like it has much to do with developing CPython itself, the
purpose of this list.
On Sep 4, 2017 2:09 PM, "TBER Abdelmalek" wrote:
> This module implements cplx class (complex numbers) regardless to the
> built-i
python-dev the next step
would be to submit this PEP to the Steering Council. However it's not
clear to me from [2] where I should actually do that when the time comes.
--
David Foster | Seattle, WA, USA
Contributor to TypedDict support for mypy
[1]: https://www.python.org/dev/peps/p
Hi folks, PEP 655 (Required[] and NotRequired[] for TypedDict) is still
looking for feedback from core devs.
I've copied the latest PEP text at the bottom of this email to make it
easier to comment on.
Thank you for your time.
Best,
--
David Foster | Seattle, WA, USA
Contributor to Pyt
eleted.
I presume the arena allocator was introduced in the first place for a reason.
Perhaps to improve performance? By removing the arena allocator are there
potential downsides other than a performance regression?
(11)
> Reference Implementation
> ''''&
tions, because it is easy to do so.
All of the preceding clarifications have been proposed in a PR:
https://github.com/python/peps/pull/2388
Best,
--
David Foster | Seattle, WA, USA
Contributor to Python's type system
___
Python-Dev mailing li
to avoid using Optional at all.
Related: The word on the street is that "T|None" is likely to be a
favored replacement for Optional in general going forward, since it's
faster to type and doesn't require an extra import (of Optional from
typing).
Best,
--
David Foster |
would care about the kernel-level changes between _MOD
and _ADD/_DEL but that might be my own lack of imagination or
knowledge of epoll techniques.
Maybe a compromise is to ship EpollExclusveSelector for a release
without it being the default and bump it to the default after
On Thu, 2019-12-05 at 16:38 +, Mark Shannon wrote:
> Hi Everyone,
>
> Thanks for all your feedback on my proposed PEP. I've editing the PEP
> in
> light of all your comments and it is now hopefully more precise and
> with
> better justification.
>
> https://github.com/python/peps/pull/1249
I have not seen any benchmarks supporting the claim that proposed limits
would ACTUALLY have any positive performance effect. While some of the
claims of performance gain are *plausible*, I also would not be very
surprised if some of them caused performance loss.
For example, requiring bit masking
I think a much more sensible approach than mandating a limit because "who
knows, it might speed something up" would be finding the speedup first.
Probably that means one limit at a time too. E.g. maybe some patch imposes
the 1 million LOC limit and demonstrates a repeatable benchmark improvement
b
On Wed, Dec 11, 2019, 6:40 AM Mark Shannon wrote:
> Another thing I would like feedback on this:
> My justification for a single limit of one million across the board is to
> ease memorization and learning.
>
Is that sufficient justification, or would differing limits be better?
>
Absolutely not
On Wed, Dec 11, 2019, 6:40 AM Mark Shannon wrote:
> P.S. On the subject of tradeoffs, here's a bonus question:
> What, in your opinion, increase in memory consumption is acceptable for a
> 1% improvement in speed, or vice versa?
I NEVER care about memory at all... except inasmuch as it effects
I bet someone in the world has written code like:
foo = str(**dynamic-args())
And therefore, disabling "silly" combinations of arguments will break their
code occasionally.
On Sun, Dec 15, 2019, 9:09 AM Serhiy Storchaka wrote:
> Currently str() takes up to 3 arguments. All are optional and
> p
On Sun, Dec 15, 2019 at 11:28 PM Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
> * The corresponding mathematical concept is unordered and it would be
> weird to impose such as order.
>
I'm with Raymond in not wanting sets to maintain insertion (or any) order.
Even though I don't doubt
On Mon, Dec 16, 2019 at 4:06 AM Serhiy Storchaka
wrote:
> 15.12.19 16:30, David Mertz пише:
> > I bet someone in the world has written code like:
> >
> > foo = str(**dynamic_args())
> >
> > And therefore, disabling "silly" combinations of arguments wil
On Mon, Dec 16, 2019, 7:35 PM David Cuthbert wrote:
> On Mon 12/16/19, 9:59 AM, "David Mertz" wrote:
>
If some improved implementation of sets had the accidental side effects of
> making them ordered, I would still not want that to become a semantic
> guarantee.
>
On Thu, Dec 19, 2019 at 5:39 PM Nick Coghlan wrote:
> I took Larry's request a slightly different way: he has a use case where
> he wants order preservation (so built in sets aren't good), but combined
> with low cost duplicate identification and elimination and removal of
> arbitrary elements (s
Even though I was the first person in this thread to suggest
collections.OrderedSet, I'm "meh" about it now. As I read more and played
with the sortedcollections package, it seemed to me that while I might want
a set that iterated in a determinate and meaningful order moderately often,
insertion or
There is, for better or worse, no bright line about what is copyrightable.
Unfortunately, a lot of the standard is "how deep are the pockets of the
opposing party?"
If you are Oracle and you want to sue Google, code which any normal person
world consider trivial becomes precious intellectual prope
I think the "if unset" behavior is well handled by collections.ChainMap.
But I do think that fact should be prominent in any documentation of the
new dict Union operator.
On Wed, Feb 26, 2020, 11:06 AM Guido van Rossum wrote:
> On Wed, Feb 26, 2020 at 7:43 AM Claudio Jolowicz
> wrote:
>
>> In m
I've written AttributeDict a fair number of times. Each time I write it
from scratch, which is only a few lines. And I only make a silly wore about
50% of the time when I do so.
I wonder if a separate type in collections might be a more natural way to
get the desired effect. I do recognize that su
A very long time ago, I wrote an XML library (Gnosis Utilities
xml_objectify) that had this same issue, and adopted the "duality" approach
(where possible, with both dictionary and other styles also available).
JSON is sort of the new XML, and it feels like the same concern. FWIW,
LXML explicitly
Hi Guido, Pablo & Lysandros,
I'm excited about this improvement to Python, and was interested to hear
about it at the language summit as well. I happen to be friends with
Alessandro Warth, whom you cited in the PEP as developing the packrat
parsing technique you use (at least in part). I wrote t
I'm a little frustrated by the tone in which the PEP dismisses the option
that is most supported in the discussion. It fine for Brandt to have a
different preference himself, but I think it ought to be presented more
neutrally.
On Fri, May 15, 2020, 10:20 AM Steven D'Aprano
> 1. +1 itertools.zip_
On Fri, May 15, 2020 at 12:55 PM Eric V. Smith wrote:
> Also: The PEP says "At most one additional item may be consumed from one
> of the iterators when compared to normal zip usage." I think this should
> be prefaced with "If ValueError is raised ...". Also, why does it say "at
> most one additi
Ok. That's true. It's technically correct as phrased. I glossed over the
"compared to" aspect. I still think it could be made more clear.
On Fri, May 15, 2020, 4:40 PM MRAB wrote:
> On 2020-05-15 20:36, David Mertz wrote:
> > On Fri, May 15, 2020 at 12:55
I know this is late in the cycle to think of this. But I just realized the
PEP 584 does not say anything about order guarantees.
I think it is safe to assume that existing keys in dictA will not have
order modified by `dictA |= dictB`. However, the PEP does not state what
order we are given when
I comment on the PR.
On Tue, May 19, 2020 at 4:44 PM Brandt Bucher
wrote:
> Maybe I'm missing something here. The PEP specifically says:
>
> > Similarly, the iteration order of the key-value pairs in the dictionary
> will follow the same semantics as the examples above, with each newly added
> k
On Tue, Jun 2, 2020 at 8:07 AM Chris Angelico wrote:
> > Given that the only input parameters are the iterables themselves, it's
> a stretch to even consider the first two as possibilities.
>
> Why? I can conceivably imagine that zip(iter1, iter2, truncate=5)
> would consume at most 5 elements fr
On Tue, Jun 2, 2020, 9:41 AM Steve Dower
> > As is, I use islice() or a break inside a loop, but that hypothetical
> parameter might be a helpful
> > convenience.
>
> Besides, "zip(iter1, iter2, range(5))" is the same length once you include
> the extra unpack, plus it works well with earlier vers
def whereis(point):
> match point:
> case MovingPoint(0, 0):
> print("Origin")
> case MovingPoint(0, y):
> print(f"Y={y}")
> case MovingPoint(x, 0):
> print(f"X={x}")
> case MovingPoint(1, 1):
> print("Diagonal at u
I gave a longer example, but the short version is that I cannot tell from
the Class Pattern or Runtime section how class patterns interact with
properties (i.e. when access changes state).
On Wed, Jun 24, 2020, 3:45 PM Guido van Rossum wrote:
> Everyone,
>
> If you've commented and you're worrie
The commit message is simply silly. It introduces numerous contentious and
false claims that have nothing whatsoever to do with the small wording
change. It misunderstands how language, culture, history, and indeed white
supremacism, work.
I would recommend amending the commit message.
The underl
Can we simply revise the commit message to something neutral like "Removed
specific reference to Strunk and White in favor of generic urge for
language clarity."
That's all the change actually was; there's no need for the other debate or
broad political background.
On Mon, Jun 29, 2020 at 3:28 PM
On Tue, Jun 30, 2020, 8:39 AM Steven D'Aprano wrote:
> It needs to be pointed out that Thomas Wouters was recently re-elected to
> the PSF board. I think we need to know whether Thomas speaks for the entire
> PSF board.
>
That seems silly. Of course Thomas doesn't speak for the Board here, and
n
On Tue, Jun 30, 2020, 10:38 AM Piper Thunstrom
> The actual advice in The Elements of Style are mostly inoffensive when
> taken on their own, and out of context. The problem is that the Elements of
> Style (And many works like it) are built on a system of white supremacy.
> The grammarian movement
Inado-san makes a very good point.
The (English) language used in technical documents is not AAVE. It's not
Scotts-English. It's not Jamaican vernacular. It's not Indian English. But
it is ALSO not American upper-middle class, white ivy-league English.
Technical documentation is a kind of DSL wit
On Thu, Jul 2, 2020, 11:08 AM Piper Thunstrom
> Paul, this is actually a good question to ask. In general, singular "they"
> is becoming more popular. It's already used frequently for the
> singular indeterminate pronoun:
>
The first attested use of singular they in English was in 1375 CE. I'm no
On Thu, Jul 2, 2020 at 12:15 PM Paul Moore wrote:
> My understanding is that technically "he" takes a dual role in
> English, as both masculine (technical linguistics gender) 3rd person
> singular and "indeterminate" 3rd person singular (because English
> doesn't have an "indeterminate-but-not-ne
to CPython
code is an added bonus.
I've been holding this thought a little while, but since the discussion on
English dialects has been raised, I think it's a point worth making.
yours,
David
PS The issue with 'they' tends to be that it doesn't adequately convey
sing
On Thu, Jul 2, 2020 at 12:58 PM Piper Thunstrom
wrote:
> > TL;DR: It's not a recent usage; it was OK in 1375.
>
> Forgive me for not giving a detailed play by play of 15 years of
> experience specifically as a writer and editor.
> Over the last handful of decades, singular "they" has been explici
On Thu, Jul 2, 2020 at 1:36 PM David Antonini
wrote:
> Surely, if the argument is to be as inclusive and easy as possible,
> British English should be used? Things may have changed, but my impression
> is that the majority of English-second-language (ESL) speakers learn
> British
that get reached, might be better, in my opinion. I prefer to recognise and
critique, rather than erase,
'historical' history, as a rule (as opposed to git history). I think similar
damage is done in this case, when the record, and opportunity to point to and
learn from i
I'm interested in being part of said Docs group!
David
From: python-dev-requ...@python.org
Sent: Thursday, July 2, 2020 5:33 PM
To: python-dev@python.org
Subject: Python-Dev Digest, Vol 204, Issue 23
Send Python-Dev mailing list submissions to
p
t; But if
I really wanted to, I probably could have snuck in a paragraph describing
my feelings about Zorn's lemma, and inuititionistic set theory, and
well-ordered cardinals. If anyone later noticed my comment, they'd think
"David is a bit nuts." The message would kinda-sorta
On Sun, Jul 5, 2020 at 2:37 PM Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:
> > Are you saying that people who split infinitives are usually
> > black,
>
> Of course not. Base rates suggest they're mostly white.
>
I think that's not true. According to this, English speake
On Wed, Jul 8, 2020, 12:22 PM Paul Sokolovsky
> popular VHLL/scripting languages which doesn't support defining of
> constants in the core language:
>
> JavaScript has "const foo = 1;"
> PHP has "const foo = 1;"
> Perl has "use constant foo => 1;"
> Lua has "local foo = 1"
> -
>
> > - Mathema
On Wed, Jul 8, 2020, 1:00 PM Paul Sokolovsky
> Right. So, if someone would like to add something to this thread, I'd
> humbly suggest to concentrate on the lack of, and need for, of
> const-ness in the Python language core (in comparison to other languages
> or not), and usecases it enables, and n
On Wed, Jul 8, 2020, 1:50 PM Paul Sokolovsky
> > I admit I do not really understand what gain dynamic languages get from
> constants. I pretty uniformly use a common convention of ALLCAPS for
> constant names
>
> > I can easily imagine that a VM might gain speed with that information,
> but that a
I don't like consuming the iterator in the exception case. You might expect
just one, but have a fallback approach for more. You could build the safer
behavior using itertools.tee() or itertools.chain().
On Mon, Jul 27, 2020, 3:10 PM Noam Yorav-Raphael wrote:
> Hi,
>
> There's a simple function
Add my name.
From: python-dev-requ...@python.org
Sent: Sunday, August 9, 2020 11:00 AM
To: python-dev@python.org
Subject: Python-Dev Digest, Vol 205, Issue 17
Send Python-Dev mailing list submissions to
python-dev@python.org
To subscribe or unsubscribe
Three-ish questions:
1. What could this do that Macropy does not already do? (yes, I know "run
as top-level script", but that's uninspiring for me).
2. Do you have any evidence Numba developers would actually want this?! (as
claimed in draft FAQ). I know a lot of them, and teach Numba sometimes,
Thank you so much Larry, for your wonderful work.
On Thu, Oct 1, 2020 at 8:44 AM Eric V. Smith wrote:
> Thanks for all of your work, Larry. I really think it was the stability of
> these releases that helped push 3.x into dominance over 2.7.
>
> 3 version control systems. Insane!
>
> Eric
> On
On Fri, Oct 9, 2020 at 10:25 AM Charalampos Stratakis
wrote:
> Does it really matter that much in regards to the specific context? If
> someone poses problematic behavior (as it seems, as I'm not familiar with
> any specifics here), maintenance of a module should be the last of the
> worries. The
I'm sure that the large majority of the string searches I've done are in
Larry's tiny category.
However, I also think that big data needs are increasing, and things like
FASTA files can be enormously large texts that one has good reasons to
search on.
If there is a heuristic switch between algori
On Wed, Oct 14, 2020 at 7:45 PM Steven D'Aprano wrote:
> Perhaps this is a silly suggestion, but could we offer this as an
> external function in the stdlib rather than a string method?
>
That feels unworkable to me.
For one thing, the 'in' operator hits this same issue, doesn't it? But for
ano
.
If the projects look interesting to you please feel free to contact me
on the contact details below.
Thank you for your help,
Best Regards
David
Large Financial Institution - Frankfurt
Senior Python C/C++ Developer (f/m)
Tasks/Responsibilities
Software developer for a
skills here.
If the projects look interesting to you please feel free to contact me
on the contact details below.
Thank you for your help,
Best Regards
David
Large Financial Institution - Frankfurt
Senior Python C/C++ Developer (f/m)
Tasks/Responsibilities
Software
would be welcomed by the Python community?
If you don't agree then do what you have to do and report me to the
other web administrators.
Maybe you should start a list that users can join to receive project
offers? It makes sense.
Best regards
David Russell
Account Manager
FDM Group
Beet
chpad.net/~bzr/+archive/ppa
Please note that for many people in a corporate/university
environment, this is not an option. Granted, you can install it by
yourself at this point,
David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/
On Sat, Feb 21, 2009 at 3:52 PM, Stephen J. Turnbull wrote:
> David Cournapeau writes:
> > On Sat, Feb 21, 2009 at 6:21 AM, Barry Warsaw wrote:
>
> > > In both those cases, you can use the PPA:
>
> > Please note that for many people in a corporate/university
&g
rs
> *restricted to such environments* really have an impact on Python
> development to outweigh the real cost of standardizing on an older
> implementation of Bazaar to developers who would be able to use a more
> capable version?"
That was not the or
slow but compatible) git-svn to push
changes to svn. Neat and clever, but complex and possibly brittle. If
you don't have commit access then you can't push changes to svn anyway,
so you don't need the git-svn half of the setup, so you should just
git-clone Neil's repo and be hap
On Tue, Mar 24, 2009 at 6:47 AM, "Martin v. Löwis" wrote:
>already the introduction of eggs made the life worse for Debian
> package maintainers, at least initially - i.e. for a few years.
It still is, FWIW,
David
___
Python-Dev mai
o build installers which provide a good experience on all
platforms. AFAIK, It does not even exist in the commercial landscape,
so I see little chance to see this in the python ecosystem.
cheers,
David
___
Python-Dev mailing list
Python-Dev@py
sion from the system
> library or forward port them. And because they're private forks the
> developers lose out on collaborating on security, bugfixes, etc because
> they are doing their work in isolation from the other forks.
This is a purely technical problem, and can be handl
On Wed, Mar 25, 2009 at 1:45 AM, Toshio Kuratomi wrote:
> David Cournapeau wrote:
>> 2009/3/24 Toshio Kuratomi :
>>> Steve Holden wrote:
>>>
>>>> Seems to me that while all this is fine for developers and Python users
>>>> it's complete
akes
> configuration-driven (repeatable) installation of add-ons easy.
But zc.buildout is not a solution to deploy applications, right ? In
my understanding, it is a tool to deploy plone instances on
server/test machines, but that's quite a different problem from
installing "applica
try to catch these but have been
a bit preoccupied this month. Should be back now.
-- David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/a
onal)? I
wasn't paying close attention, so maybe there's some other mechanism
in place at this point?
-- David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
d even use the
> multi-version option for setuptools: I don't see any sane way to
> install conflicting requirements into a shared 'site-packages'.
But that's the problem: it often happens *even if you don't use
setuptools yourself*. I would not be surprised if that&
x27;t and shouldn't prevent it totally, and tools are
already there to help minimizing the problems of bundling. For
multiple system-wide libraries, I have yet to encounter anything which
makes it somewhat reliable - it has only caused problems for me, and
not solved any single problem.
201 - 300 of 1990 matches
Mail list logo
