I think it’s fine to say that Python 2 EOL is on January 1, 2020. That doesn’t
preclude a Contractual Obligation release in April. There’s precedence in the
last Python 1 (1.6.1) release!
https://en.wikipedia.org/wiki/Monty_Python%27s_Contractual_Obligation_Album
-Barry
> On Sep 10, 2
This is mostly just a test of the new python-dev footer. We’ve added a link to
the CoC into the footer of the message… hopeful!
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To
is is a kind of thing
> that makes the ML obsolete and forces everyone into discourse.
Doko, as to the substance of PEP 602, does the annual release cadence in
October cause problems for Ubuntu?
-Barry
signature.asc
Description: Message signed with OpenPGP
__
reakages, regressions, and other problems during the
Python beta process. How can that be leveraged better?
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send
to be
> proceeding.
I’ve always expected that 4.0 would be reserved for such incompatible C API
changes.
I remember we had a similar discussion when 2.7.x was rolling over to x > 9.
We didn’t bump it to 2.8 then, so I think we should just be prepared for Python
3.10 when the time comes.
compatibility
> with 2.7. When we are going to deprecate and remove the "u" prefix?
I think removing or even deprecating it will cause unnecessary code churn in
third party libraries, for very little value. Let’s just call it a wart until
Python 4000.
-Barry
signature.asc
Descr
now. I will shortly be submitting and merging a PR to official
reject both PEPs.
-Barry, on behalf of the Python Steering Council
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To
.org/3/library/string.html#template-strings
flufl.i18n - https://flufli18n.readthedocs.io/en/latest/
I’m not convinced that PEP 501 would provide much benefit on the technical side.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
__
/reference/index.html), then the PEP needs to state
that, and feedback from other implementation developers should be requested.
Cheers,
-Barry
> On Dec 5, 2019, at 08:38, Mark Shannon wrote:
>
> Hi Everyone,
>
> Thanks for all your feedback on my proposed PEP. I've editing the PE
PEP. When the PEP author is
ready for a pronouncement, you can email the Steering Council.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to
guarantees for
both sets and dicts. The Library Reference does document the ordering
semantics for both dicts and sets, but I wouldn’t say that information is easy
to find. Maybe we can make the latter more clear too.
Cheers,
-Barry
> On Dec 16, 2019, at 09:57, David Mertz wrote:
>
&g
retroguessing
that we created dev@ first, then quickly rethought the name, created
python-dev@ and retired dev@.
-Barry
> On Jan 1, 2020, at 08:51, Mark Sapiro wrote:
>
> On 1/1/20 8:42 AM, Nick Coghlan wrote:
>> On Thu, 2 Jan 2020 at 02:24, Skip Montanaro wrote:
>>>
>>&g
remember more details.
I kind of doubt those original Majordomo archives have survived the various
hosting migrations since then, but maybe they are laying around on
mail.python.org some place?
-Barry
> On Jan 6, 2020, at 06:48, Skip Montanaro wrote:
>
> On Wed, Jan 1, 2020 at 7:2
d all the python 3's.
I have all the python versions installed on my build systems
side-by-side. I did not need to use venv as all the python's
are installled into the systems.
Maybe you can use some of the ideas from the code.
See this module:
https://svn.code.sf.net/p/pysvn/code/trunk/py
No objections here either. CC’ing postmaster.
-Barry
> On Jan 14, 2020, at 07:06, Facundo Batista wrote:
>
> El dom., 23 de dic. de 2018 a la(s) 14:20, Barry Warsaw
> (ba...@python.org) escribió:
>>
>> On Dec 23, 2018, at 07:29, Facundo Batista wrote:
>>>
t a
> general policy to decide if a deprecated feature should stay until
> 3.10, or if it's ok to remove it in 3.9.
Given that we’ve changed the release cadence to one major release per year, it
doesn’t seem that much of a burden to revert and carry these changes forward
into Py
e. Other projects may have made the similar decisions.
Barry
> Victor
>
> Le ven. 24 janv. 2020 à 09:19, Chris Angelico a écrit :
>>
>> On Fri, Jan 24, 2020 at 7:05 PM Victor Stinner wrote:
>>> We kept a compatibility layer with Python 2 on purpose, PEP 4 says
On Jan 27, 2020, at 13:56, Barry Scott wrote:
>
> Isn't there going to be a final Python 2.7 release in April 2020?
Yes, but I’ve been calling it a “celebratory release”. We’re gonna party at
Pycon like it’s 2000.
-Barry
signature.asc
Description: Message signed w
.
-Barry (on behalf of the Python Steering Council)
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3
By unanimous consent, the Python Steering Council unanimously accepts PEP 614 —
Relaxing Grammar Restrictions On Decorators.
Congratulations to PEP author Brandt and PEP sponsor Guido, and thanks to
everyone who’s worked on this PEP and its implementation.
Cheers,
-Barry
signature.asc
;> anyone embedding is forced into *significantly* more code as a result.
>
> Putting a value in a function-local variable enforces stronger restrictions
> than putting it in a thread-local variable.
>
> I am proposing that we *don't* change the API. How does that
eta. Since that is counter
to our general policy, we would need to get explicit RM approval for such a
change.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe s
e better policy-wise if
the new parser were the default in time for the first beta rather than after.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe se
efinder.py", line 343, in load_module
co = compile(fp.read()+'\n', pathname, 'exec')
File "C:\Python38.win32\lib\encodings\cp1252.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap'
> On 11 Apr 2020, at 16:28, Barry Scott wrote:
>
> modulefinder.py does not open source files in "rb" which
> prevents compile() from applying the encoding rules.
>
snip
I have created the bpo, the pr and have the checks passing except that I need a
NEWS.d entry
to
> On 12 Apr 2020, at 21:49, Eric V. Smith wrote:
>
> On 4/12/2020 4:08 PM, Barry Scott wrote:
>>
>>> On 11 Apr 2020, at 16:28, Barry Scott >> <mailto:ba...@barrys-emacs.org>> wrote:
>>>
>>> modulefinder.py does not open source fil
questions and concerns. We look forward to its
availability in Python 3.9. Thank you Paul, and everyone who helped contribute
to this important new module.
Cheers,
-Barry (on behalf of the Python Steering Council)
signature.asc
Description: Message signed with OpenPGP
No objections here.
-Barry
> On Apr 29, 2020, at 06:05, Paul Ganssle wrote:
>
> Signed PGP part
> Hi all,
>
> PEP 615 specifies that we will add a first party tzdata package. I created
> this package at pganssle/tzdata, but I believe the final home for it should
&g
on a service that forks slave processes to handle I/O
transactions.
There is a monitor process that manages the total memory of all slaves and
shutdown and replaces
slaves when they use too much memory. Typically there are 60 to 100 slaves with
a core each to play with.
Th
3.10 and 3.11, Pablo will also help to continually
improve the process of selecting and serving as release manager.
Please join me in welcoming Pablo in his new role!
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev
uot;3.10.0 final: Monday, 2021-10-04" to revert
> incompatible changes which caused most troubles.
>
snip
My experience with keeping PyCXX up to date with these changes is that its not
hard
to be compatible. I support python 3.4 to 3.9 for limited and unlimited API.
(I also support py
with an emitted warning, or promoted to a full-on feature supported in
the language.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python
` is also a soft keyword. I’m guessing it must
be.
Those are my current thoughts on first read through.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send
could support this syntax:
case in 401, 403, 404:
That seems like it would be both unambiguous and semantically obvious.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.o
is simply
> preventing an error, rather than making one otherwise-valid name
> special.
I thought of that too as I was reading the PEP, but forgot to add it to my
notes. I do like ellipsis more than underscore here.
-Barry
signature.asc
Description: Message signed with OpenPGP
On Jun 23, 2020, at 13:50, Ethan Furman wrote:
>
> On 06/23/2020 12:49 PM, Barry Warsaw wrote:
>
>> Maybe the PEP could support this syntax:
>> case in 401, 403, 404:
>> That seems like it would be both unambiguous and semantically obvious.
>
> Unfort
mirrors try/except and if/elif/else constructs so it looks quite natural.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-
On Jun 23, 2020, at 23:25, Emily Bowman wrote:
> I wonder if it's time to officially designate _ as a reserved name.
That would break the i18n use case.
Cheers,
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev
comments made on this thread. Thank you, and I look
forward to the updated PEP.
> On Tue, Jun 23, 2020 at 12:07 PM Barry Warsaw wrote:
> Couldn’t you adopt a flat indentation scheme with the minor change of moving
> the expression into a `match:` clause? E.g.
>
> mat
ll the 8-bit char sets.
Why is it needed?
Barry
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://ma
Once I add that support to PyCXX all my users should easily port to a
non-Py_UNICODE world.
Barry
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/pyt
nk it reads better.
as expression
case …
I still wish cases lined up under match, but it’s not a deal breaker for me.
-Barry
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscrib
. You can use the same technics for unix systems.
1. Start with standard python
2. pip install deps
3. run tool to create minimum app
If you build multiple apps then you can share common files to cut down size as
well.
Barry
> On 22 Jul 2020, at 14:31, Huang, Yang wrote:
>
> Thank yo
PEP 622 is already on the SC’s agenda for review.
-Barry
> On Aug 5, 2020, at 09:47, Ethan Furman wrote:
>
> On 7/30/20 8:35 AM, Rob Cliffe via Python-Dev wrote:
>
>> The debate is still going on as to whether "capture" variables should be
>> marked...
&
Linking to a PEP for the historical record is fine, but let’s please make it
clear that the PEP is both not the documentation for any feature, and may
indeed be out of date. PEPs are deliberately not updated as features evolve.
Cheers,
-Barry
> On Sep 14, 2020, at 09:38, David Antonini wr
!
Cheers,
-Barry (on behalf of the PSC and PSF)
signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3
Seems fine to me. It’s an easy process; just ask postmaster@ and they can shut
the list down, retaining the archives read-only for posterity.
-Barry
> On Oct 13, 2020, at 09:26, Eric V. Smith wrote:
>
> Would anyone care if Import-SIG was shut down? It gets a few spam emails per
&
is way for about 24 hours, I will tag the branch
at about 2300 UTC Thursday February 12 so that Martin can build the
Windows installers on his Friday morning. Then Friday evening at
about 2300 UTC, I will spin the tarballs and make the release.
Cheers,
Barry
-BEGIN PGP SIGNATURE-
Vers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 12, 2009, at 7:52 AM, Benjamin Peterson wrote:
On Thu, Feb 12, 2009 at 6:28 AM, Daniel (ajax) Diniz
wrote:
Barry Warsaw wrote:
A quick reminder that I am planning to release Python 3.0.1 this
Friday, February 13.
Cool :)
Should I
mainly. I have no problem holding off.
The documentation change is probably safe. Given that I'm tagging
3.0.1 in about 4.5 hours, please be very conservative with any other
changes.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZRtMnEjvBPtnXfVAQ
ack it out.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZRxDnEjvBPtnXfVAQLJCQP/d+BUqjwxHDyK0Dv8i7TlgoYfjHCgCu/M
zQVrMihB3lyoem7os2VdGubButLwOoMP69uU9Rieo62Fag1bxF6ME2HJC6dgJ3ge
xUwRD+01hCkkWNeONdYN/cANjkezE7i4O9z7YyGVJuktO3ZbdY/vjYbY/HE2ZrGK
+wguhd06tA0=
=c6q3
--
il package.
Those of you who are going to Pycon, is anybody available to sprint a
bit on email?
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZVz7nEjvBPtnXfVAQK7nwQArJMjC9TVxnuuZ+4kBBD3+1pqyXbnRKa/
/nuWCfrqsW5z/RGxWdPjHf/02TCdGXsnRwGhE8bjDgawL0VnO1lTZI
see the Python 3.0.1 release page:
http://www.python.org/download/releases/3.0.1/
To report bugs in Python 3.0.1, please submit them to the issue
tracker at:
http://bugs.python.org/
Enjoy!
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZYpSnEj
(a) happens it's okay if the 3.0 branch is left alone until
the time we need to make that one patch. The probability of (b) is
low, so let's worry about that when it happens, and let's try not to
make it happen. :-)
That's more than fine with me! :)
Barry
-BEGIN PGP SI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 13, 2009, at 11:46 PM, Benjamin Kaplan wrote:
Any chance of getting a Mac installer for this one?
I believe Ronald is planning to upload it soon.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin
hould
concentrate on making that a great release without worrying about also
trying to get 2.7 out.
:Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZrJ7HEjvBPtnXfVAQJEKAP/fQ/SWqCNYmPQreBdN4Y7BKC4+K0f9Kk6
7DuVEyjd/BI9luqLxeGgZFdm9cwBXNkrSQ0Vw9wGx5rjGWRxPhAzWPh3tSE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thinking again about 3.0.2.
If we'd like to do bug fix releases before Pycon, I suggest Monday
March 9th for code freeze and tagging. That would mean a Tuesday
March 10th release.
What do you think?
Barry
-BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 18, 2009, at 1:49 AM, Brett Cannon wrote:
If there are really enough fixes to warrant it, sure. Otherwise
would it be
worth more to just wait until after PyCon where there is a bigger
chance of
fixed issues?
Good point.
Barry
upgrading your client to at
least bzr 1.9 would be a hardship, please contact me. If I don't hear
any objections by say Tuesday, I'll go ahead and do the repo upgrades.
Thanks,
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZ7HwHEjvBPtnXfVAQIlxAQAk0ze8AH
h the participants would have to manage persistency themselves.
A DVCS would probably work too, given these are almost entirely text
files.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSZ76AXEjvBPtnXfVAQIx5QQAs29FVEYDjbcvG2vLB3RtuuLOwahECP2Q
Yyxvz26mRgOeCX/4rfa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 20, 2009, at 10:09 AM, Barry Warsaw wrote:
I've just upgraded the Bazaar mirrors on code.python.org to use bzr
1.12. We now have the opportunity to upgrade the repository format
for better performance. Because of the bzr-svn requir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 7:15 AM, Stephen J. Turnbull wrote:
Besides, if Barry makes this experiment *now* and enough people speak
up that it will make it difficult for them to contribute to Python,
the Bazaar proponents can revert to an older version
should be the case with Bazaar and I assume Mercurial or Git. I
just offered up the PPA for folks like me who are root but lazy. :)
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSaBk33EjvBPtnXfVAQI4sgP+LST/04wpPdckq++BLt5rpeCNfFomu+Zi
ea/wWcVvaEOe5qX+wBuzV7
ience working on PEP
0374. Maybe Brett, Barry, or Alexandre would like to comment?
My only comment is that Google docs did not always work correctly for
me. E.g. at some point toward the end of the process, I lost the
ability to add comments. But hey, it's a big pile of JavaScript
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 3:35 PM, Jeroen Ruigrok van der Werven wrote:
-On [20090221 21:30], Barry Warsaw (ba...@python.org) wrote:
I think no matter what DVCS gets chosen
Isn't that getting ahead of the game? I thought that the choice
wheth
seems
very prone to this "upgrade the server and the clients need to be
upgraded too" cycle.
That's not what we're talking about. This is a case of older clients
not understanding a newer repository format.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 20, 2009, at 10:09 AM, Barry Warsaw wrote:
I've just upgraded the Bazaar mirrors on code.python.org to use bzr
1.12. We now have the opportunity to upgrade the repository format
for better performance. Because of the bzr-svn requir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2009, at 2:03 PM, Mark Dickinson wrote:
On Wed, Feb 25, 2009 at 2:23 PM, Barry Warsaw
wrote:
This is now done. Please let me know if you have any problems with
the
mirrors.
Is the cron job that's supposed to update th
itted with this one:
http://bugs.python.org/issue1974
Barry usually takes ownership of changes to the email package.
Do you have patches ready for him to review?
Not yet for 1974, but given that I submitted a patch for this issue:
http://bugs.python.org/issue4308
...some months ago, and nothin
o the wiki.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSag4V3EjvBPtnXfVAQLTMQP9EUHzd+C0aOdwISI3ckTz2aZxyWhM2/M3
yyBY8/WTEa2gJbFePX6Qk+JS33/B3FYbcKRBpjfKlaTp9DLlVdSZoQ2sA/gD27sE
82SxuxbjnjtR+513xIX2P1WflOA1SxpfKgOs9c4Gxkuee1eUgv2A5LKX5PlaE/oX
sPKVgQk7hw0=
=/Ipw
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2009, at 2:03 PM, Mark Dickinson wrote:
On Wed, Feb 25, 2009 at 2:23 PM, Barry Warsaw
wrote:
This is now done. Please let me know if you have any problems with
the
mirrors.
Is the cron job that's supposed to update th
t folks can fill out there own links.
Thoughts?
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSahm9XEjvBPtnXfVAQKYTwP/QzLWj5E8zrqwh2Wd50imAdbtricUEOOX
32r2vSMZ0P4LwFuIKHSFNT3FLsn1p254Os0tD/05RAVEvVxuOkd9w7Hn+Vn75yG2
trkK356ESUfJFtGttFUhXD6z2fpKP23u+dZV/OtDQWqpZSg59wkDL
: it's just a
list with linear searching for key lookup. Messages should not have a
billion headers. ;)
Have you or Armin considered the possibility of wanting both the
defaultdict and odict behavior in, say a mixin subclass?
Barry
-BEGIN PGP SIGNATURE-
Vers
to the wiki.
See
* http://wiki.python.org/moin/FrontPage
* http://wiki.python.org/moin/Bazaar
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSaxsjXEjvBPtnXfVAQIqpQP9HHXHzbXG5D51QeKr3B9F4AppINrznndC
Jam/IN+zuy+nm0T8Tq41rCqywuQm5Cj5+oBI6U5pQj58nQ6YAJzBYuJ1/mmRZOYv
0fTzIt0O
FWIW, I use smtpd.py and a few of the asyncore APIs
(.loop(), .socket_map.clear(), and .close_all()) in the Mailman 3 test
suite. That only works on Python 2.6 and I don't recall even a hiccup
when moving from 2.5 to 2.6.
Barry
-BEGIN PGP SIGNATURE-
Vers
o, do you know where your time machine keys are? :)
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSbAaRHEjvBPtnXfVAQK3nQP/Uz6CF7zxIbTJWHyGyPBr1+pUTESzryNs
SKnBwcyIjYw/+7whtdfp31jbgsv+FcZ9YmMx7haUzPS/lKaRClvfUlirXe
This is a Python-wide policy.
When Python 2.7 is released, there will be one last 2.6.x bug fix
release, and then it will go into security-only mode. Similarly, when
Python 3.1 is released, there will be one last 3.0.x release and it
too will go into security-only mode.
Barry
-BEGI
n 3.1.
Congratulations on your first baby! Here's to hoping you release
many
more of these!
Yes, well done, Benjamin. Barry Warsaw is walking with a spring in his
steps again ;-)
I was wondering why the weather here in DC has turned so beautiful
after last week's snow storm!
Barry
llowing the
instructions on the the wiki page.
Perhaps RDM branched from code.python.org before I upgraded the
repository format to 1.9-rich-root?
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSbUIcnEjvBPtnXfVAQI47AP/QdS/7qyrGXseNsDYLIl/aRC4DV3HOBxm
G4721SchQAw8CF6z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 9, 2009, at 9:02 AM, R. David Murray wrote:
On Mon, 9 Mar 2009 at 08:15, Barry Warsaw wrote:
On Mar 9, 2009, at 1:26 AM, Andrew Bennetts wrote:
On the other hand, it does appear that
<https://code.launchpad.net/~rdmurray/python/bug5450&
rename
dance if appropriate, and fortunately it's easy enough to implement in
Python. Mailman's queue runner has done exactly this for ages.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCUAwUBSbbSXHEjvBPtnXfVAQLrsQP2NxJL+
rrectly on Linux.
Of course, a careful *nix application can ensure that the file owners
and mod bits are set the way it needs them to be set. A convenience
function might be useful though.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSbbb8XEjvBPtnXfVAQLxvgP/SDn
lugin installed, you can now do:
bzr branch py:trunk
or to get the 2.6 branch you can do:
bzr branch py:2.6
You can also use this to get user branches, e.g. my email rewrite
branch:
bzr branch py:~barry/30email
If you have write access to branches on code.python.org, you can
rg/dev/workflow/ . So now
people
who ever triage issues have a guide to follow if they are not sure
how
to set things.
Does that mean PEP 3 should be Withdrawn or does it mean it should be
replaced?
It should probably be replaced with Brett's document.
Barry
-BEGIN PGP SIGNATURE--
package manager.
Tools like setuptools, zc.buildout, etc. seem great for developers but
not very good for distributions. At last year's Pycon I think there
was agreement from the Linux distributors that distutils, etc. just
wasn't very useful for them.
Barry
-BEGIN PGP SIGNATURE--
ploying actual Zope-the-web-thing I just want to install it from my
distro and be done with it. It's up to my distro to determine
compatibility, handle bug and security fixing, etc.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScpFj3EjvBPtnXfVAQJakwP/djOrhp
with other developers. My hope of course is that the
setup.py is useful to distros who want to include my package in their
offering.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScq4enEjvBPtnXfVAQIOpAP/bJsMn7iKyIOhm8iGxWfeNhtaesCXy2MZ
eU8KyI0xvtACleLzzZd
icult to work with for plugins, and I
think the Python ecosystem could benefit from more shared wisdom, if
not code, in designing plugin frameworks for applications.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScq5b3EjvBPtnXfVAQIdDAP+OHWHqbYhpAuokfOQ4
ul (I hope) but
there won't be much further decomposition into smaller sharable parts.
Does Twisted's monolithic package structure stem from a similar pattern?
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScq7MXEjvBPtnXfVAQIUFwP/efivE5nTcEF/xhL6FgfJ41/vhWiI1jKY
thon from source, say into the default /usr/local and
started easy_installing stuff into there, it was possible to break
your system Python. This was because the system Python hacked /usr/
local's site-packages into sys.path. That's now been fixed.
Barry
-BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 25, 2009, at 6:24 PM, P.J. Eby wrote:
At 06:08 PM 3/25/2009 -0500, Barry Warsaw wrote:
I've found setuptools entry points difficult to work with for
plugins,
I'd be interested in hearing more about your specific difficulties,
ection.
Think: the package-y flavor of
os.listdir(os.path.dirname(package.__file__))
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScvV8HEjvBPtnXfVAQIvdQP/dwzTsPLVtM4eAKLRfzJHG7mToNVDgHNn
4L6Kh99sScVOpeYPw8tltX5YAFwDeysIiD
n
patterns.)
Good idea. Thinking back on my typical use cases, a glob style
pattern would be enough. Usually I'm asking "give me all the .py
files in this package" or "I'm looking for the .txt files in this path".
Barry
-BEGIN PGP SIGN
.
That works for me!
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScvcTHEjvBPtnXfVAQLEAAP+MmMW3yzIYK5mT+YauzReV10UYFDkLhvT
ALbKI6+NFKu6aMYBWe70QqXYxmau3XpZyUD6qzg32t7J2kTJfoLWRCAzv9XLv6/0
Qu33AVZ7yYasSW/tbpHeDvBYsJAM3ANjYRCI4v1G35gZ8HFgdQwEnviYNW1nB/yt
3lguOFPoT6c=
=/CuU
e one place that
I've had
to
drop down to file system introspection.
Really ... ? What are all these for ?
E.g. find all the doctests under foo.bar.docs
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScvc9XEjvBPtnXfVAQJT8AP/QhT6Pm4xEL+Bas96cD9waG
uld support putting pkg_resources in the
stdlib.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBScvdH3EjvBPtnXfVAQKDvQP7B8/POejfswQ8A+Xl4+XJQiO8xHpyPUbC
wpja12gXhamSvBxgoKnFCeTzMgdEoaeK838CR4yvn9YBM7hzJWW0seODG7JpmxGp
w9RXDaf1BuFuxdtTZ8qsoNzRtFQ0LOEh5HtnHYVcpwDHg9FMOKu4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2009, at 3:07 PM, Olemis Lang wrote:
On Thu, Mar 26, 2009 at 2:52 PM, Barry Warsaw
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2009, at 2:43 PM, Olemis Lang wrote:
One thing that /would/ be helpful though is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2009, at 3:14 PM, Olemis Lang wrote:
On Thu, Mar 26, 2009 at 2:53 PM, Barry Warsaw
wrote:
BTW, under a better name, I would support putting pkg_resources in
the
stdlib.
... or a subset of it ? or integrating its features with
this.
Yes, it should look inside a package. Very often, a data directory
will be made a package through the addition of a __init__.py just so
the data can be found. There are often no other py files in such data
packages.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin
rce.resource_listdir() that I was missing.
Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSc1B6HEjvBPtnXfVAQI39wP/VZ4m7x8hd6HzI4VFetFwe/zgLxIJO5Wt
adpQEv/hou+JVgRxSaa0mNAzZSVzDw8pDa2aZ0RXeM/fEaSnhX2IUh+28gNvhyMZ
m+57LF5GZMxJsV2fYNj6ELFKeC/JXCQYB43Fxs7AShzlP/1LRnrN9Lnt
901 - 1000 of 2826 matches
Mail list logo
