I merged a PR (https://github.com/python/psf-salt/pull/234) that was
supposed to disable it, but apparently it's not enough.
I'll double check with Ee (added to cc).
There is also a new script to replace the old one that is waiting for
reviews (see https://github.com/psf/gh-migration/issues/6 and
The migration from bugs.python.org to GitHub is now officially
complete, and all the issues have been successfully transferred.
You can read the full announcement here:
https://discuss.python.org/t/github-issues-are-now-live/14967
Best Regards,
Ezio Melotti
comment using GitHub Issues.
bpo will remain available in read-only mode.
For live updates, see
https://discuss.python.org/t/github-issues-migration-status-update/14573
Best Regards,
Ezio Melotti
___
Python-Dev mailing list -- python-dev@python.org
To
Sorry, my mistake (again :)
As mentioned in an earlier python-dev thread, I'm working on the
bugs.python.org -> GitHub issues migration, and while testing I have
to delete and recreate the repo for each iteration. Since the repo is
private, in order to get feedback from fellow core-devs and triag
Hi Victor,
On Thu, Dec 2, 2021 at 11:48 AM Victor Stinner wrote:
>
> Hi Ezio,
>
> What is the status of migrating Python issues to GitHub?
You can check the status here: https://github.com/psf/gh-migration/projects/1
> Is it done?
Not yet, but we are aiming for mid-January.
> If not, what are
Hi Larry!
The steering council brought this thread (that I missed) up to my attention.
On Thu, Nov 4, 2021 at 8:17 AM Larry Hastings wrote:
>
> I guess this is part of the migration from bpo to GitHub issues?
It is: this is one of the repos that I'm using for testing. In
particular I'm using it
tes.
During the next phase I will work with the WG to sort out all the
major issues that we might encounter, and then I will once again reach
out to you to gather feedback from the wider audience that follows
these mailing lists.
Best Regards,
Ezio Melotti
__
On Wed, Jul 17, 2019 at 2:36 AM Brett Cannon wrote:
>
> Jeroen Demeyer wrote:
> > I have seen multiple discussions where somebody wants to deprecate a
> > useless function but somebody else complains that we cannot do that
> > because the function in question cannot be removed (because of backward
ik the only way to inform users on
GitHub Issues is writing another bot that adds messages) and backlash;
* doing separate specific tests (e.g. having a read-only repo with all
the issues to test search/navigation, and a separate read-write repo
to test issue creation) or a "real-world" tes
On Thu, May 23, 2019 at 10:17 PM Ezio Melotti wrote:
>
> Hello,
> Berker and I have been working on a PEP that suggests we keep using
> and improving bugs.python.org and Roundup instead of switching to
> GitHub Issues as proposed by PEP 581.
>
> The PEP covers:
> * Wh
On Fri, May 24, 2019, 23:14 Gregory P. Smith wrote:
>
>
> On Fri, May 24, 2019 at 1:48 PM Ezio Melotti
> wrote:
>
>>
>> On Fri, May 24, 2019, 20:23 Gregory P. Smith wrote:
>>
>>> -cc: committers to avoid crossposting.
>>>
>>
>> +
t; I'm not going to try proposing a PR to this PEP encapsulating that, I'll
> leave that up to anyone willing to wrangle such a PEP. The list archive
> has it regardless now. :)
>
Thanks a lot for the feedback, I'll update the PEP once I get back to a PC
(using mobile now).
://www.python.org/dev/peps/pep-0588/
The full text of the PEP is include below. We are planning to update
the PEP to include the feedback we receive and to update the status of
features as we implement them (we also have a Google Summer of Code
students working on it).
Best Regards,
Ezio Melotti
ansparent, without
considering some of the concerns.
(This might also be a symptom of a wider problem caused by the
fragmentation of the discussions between the old MLs, discuss, zulip,
IRC, GitHub PRs and issues, and IRL meetings, but this is a separate
topic.)
Best Regards,
Ezio Melotti
On Fri, Mar 1, 2019 at 8:05 AM Ezio Melotti wrote:
>
> On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy wrote:
> >
> > On 2/28/2019 6:54 PM, Glenn Linderman wrote:
> >
> > > There seems to be enough evidence that something went wrong somewhere,
> > > though,
On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy wrote:
>
> On 2/28/2019 6:54 PM, Glenn Linderman wrote:
>
> > There seems to be enough evidence that something went wrong somewhere,
> > though, and whoever maintains that process should start investigating,
> > but it would still be nice to get confirmat
ks to John Rouillard (from the Roundup team) and R. David Murray
for the help!
Best Regards,
Ezio Melotti
P.S. Roundup started moving towards Python 3.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
U
s
> Raúl Núñez de Arenas
>
This already looks like UTF-8 -- you should be able to verify this by
manually selecting UTF-8 as encoding from the menu.
If the Content-Type still uses us-ascii though, it should be fixed to
specify UTF-8 instead.
Best Regards,
Ezio Melotti
> I a
W I only consider simple documentation issues and typo/whitespace
fixes as "trivial", YMMV.
Best Regards,
Ezio Melotti
> --
> --Guido van Rossum (python.org/~guido)
>
___
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
.python.org/cpython/file/default/Lib/test/support/__init__.py#l2202
http://bugs.python.org/issue11732
http://bugs.python.org/issue18948
http://bugs.python.org/issue23314
Perhaps Mac OS has something similar too?
Best Regards,
Ezio Melotti
>
> but as far as I could tell, in all cases t
e helpful.
Best Regards,
Ezio Melotti
> Saul Shanabrook
>
___
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
r('issue', open_issues, dict(type=6))) # enhancement
1557
>>> len(x.filter('issue', open_issues, dict(type=1))) # crash
122
>>> len(x.filter('issue', open_issues, dict(type=2))) # compile error
141
>>> len(x.filter('issue', open_issu
each status/type), but other things are a bit
more complicated (e.g. things involving specific periods of time) and
currently the roundup-summary takes a few minutes to analyze all the
issues.
I also tried to include just a few useful charts on the stats page --
at first I had several more charts but
raph you can see that out of the 4500+ open issues,
about 2000 have a patch.
We need more reviewers and committers :)
Best Regards,
Ezio Melotti
>
> Regards,
> francis
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org
Hi,
I added a new "stats" page to the bug tracker:
http://bugs.python.org/issue?@template=stats
The page can be reached from the sidebar of the bug tracker: Summaries -> Stats
The data are updated once a week, together with the Summary of Python
tracker issues.
Best Regards,
ough):
http://bugs.python.org/issue?@template=stats
Best Regards,
Ezio Melotti
> Regards,
> francis
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/
ome interesting discussion about it).
Best Regards,
Ezio Melotti
> (the subprocess docs are
> an example of implicitly communicating that the module is dangerous
> and unusable).
>
> The preferred form of documentation is to be affirmatively worded,
> telling how to use a tool co
de to backport it, you will have to
do a null merge and it gets slightly more complicated.
Best Regards,
Ezio Melotti
___
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
est 3.x release that is supported?
What happens if this addition will still not push people to move their
code to 3.x and similar requests are made for 3.6+ (and shift what I
just said for another 18 months)?
Best Regards,
Ezio Melotti
>
>
> --
> Steven
"/tmp/foo.py", line 7, in
import email
File "", line 1561, in _find_and_load
File "", line 1519, in _find_and_load_unlocked
File "", line 1473, in _find_module
File "", line 1308, in find_module
File "", line 1284, in _ge
Lists are mutable, and
their elements are usually homogeneous and are accessed by iterating
over the list.
"""
Best Regards,
Ezio Melotti
> probably
> at the point when people have learned enough to be designing their own
> programs where this issue comes up -- before the
On Sun, Feb 16, 2014 at 11:06 AM, Georg Brandl wrote:
> Am 16.02.2014 09:40, schrieb Ezio Melotti:
>> Hi,
>>
>> On Sun, May 5, 2013 at 7:45 AM, Ezio Melotti wrote:
>>> Hi,
>>>
>>> On Sun, May 5, 2013 at 4:23 AM, Tim Delaney
>>
Hi,
On Sun, May 5, 2013 at 7:45 AM, Ezio Melotti wrote:
> Hi,
>
> On Sun, May 5, 2013 at 4:23 AM, Tim Delaney
> wrote:
>> It appears there's no obvious link from bugs.python.org to the contributor
>> agreement - you need to go via the unintuitive link Foundation
Nick
suggested me to bring this up again. Nick also suggested to document
our deprecation policy in PEP 5 (Guidelines for Language Evolution:
http://www.python.org/dev/peps/pep-0005/ ).
I'm including below the full text of the original email.
Best Regards,
Ez
On Wed, Oct 9, 2013 at 8:15 AM, Georg Brandl wrote:
>
> [...]
>
> Rather, I would try to make as many C functions as possible "regular",
See http://bugs.python.org/issue8706 and http://bugs.python.org/issue8350
Best Regards,
Ezio Melotti
On Thu, Aug 22, 2013 at 7:45 PM, Donald Stufft wrote:
>
> On Aug 22, 2013, at 1:34 PM, Ezio Melotti wrote:
>
>> Hi,
>>
>> On Thu, Aug 22, 2013 at 1:00 PM, Petri Lehtinen wrote:
>>>
>>> Removing some cruft on each release can be very painful for use
time to update their
code.
The second group is responsible to listen to the warnings and update
their code accordingly.
The third group is responsible to sit back and enjoy our hard work
without seeing warnings/errors.
Best Regards,
Ezio Melotti
>
> --David
>
> PS: When thinking about
l you what to change.
If you have good test coverage this should happen automatically (at
least with unittest), but even if you don't you should run your code
with -Wa before upgrading (or test your code on the new version before
upgrading Python/Django/etc. in production).
Best Regards,
Ezio Me
t turn deprecations on by
> default when running your tests but leave them silent otherwise.
>
http://bugs.python.org/issue10535
(I put the keys of the time machine back at their usual place)
Best Regards,
Ezio Melotti
> I still think keeping them silent for the benefit of end-users is
ings, but will for those who haven't. The question
> then becomes, is it better to "bundle" these removals into the
> Python 4 release, or do them incrementally?
>
A while ago I wrote an email to python-dev about our deprecation policy:
http://mail.python.org/pipermail/
ot the one you committed)
hg up csid-of-the-other-head
# merge your changes on with the ones you pulled
hg merge
This will merge the changes you just committed with the ones you
pulled, and result in a shorter diff that is easier to
read/review/merge.
Otherwise pulling and updating before committing will avoid the
problem entirely (unless you end up in a push-race).
Best Regards,
Ezio Melotti
___
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
rt using the right ones and convert
the wrong ones when they come across them.
Best Regards,
Ezio Melotti
[0]: http://en.wikipedia.org/wiki/Dash
[1]:
https://bitbucket.org/birkenfeld/sphinx/src/default/sphinx/util/smartypants.py#cl-261
___
Python-Dev
aning, including buffer objects.
"string" means "str", "bytes" means "bytes", "bytes-like object" means
"any object that supports the buffer protocol" [0] (including bytes).
"string and bytes-like object" includes all of them.
I
rking HOWTO" that covers generic topics
could/should be added to docs.python.org.
Best Regards,
Ezio Melotti
> What would you add/subtract from the
> above? How important is testing memory performance? How do we avoid
> performance
en you add a
> patch to the tracker).
>
> I'd suggest that if the "Contributor Form Received" field is "No" in user
> details, there be a link to http://www.python.org/psf/contrib/.
>
See http://psf.upfronthosting.co.z
+
> +.. _defusedxml: <https://pypi.python.org/pypi/defusedxml/>
> +.. _defusedexpat: <https://pypi.python.org/pypi/defusedexpat/>
> +.. _Billion Laughs: http://en.wikipedia.org/wiki/Billion_laughs
> +.. _ZIP bomb: http://en.wikipedia.org/wiki/Zip_bomb
> +.. _DTD: http://en.wikipedia
On Mon, Mar 11, 2013 at 3:14 AM, Ezio Melotti wrote:
> Hi,
>
> On Mon, Mar 11, 2013 at 2:58 AM, raymond.hettinger
> wrote:
>> http://hg.python.org/cpython/rev/0f86b51f8f8b
>> changeset: 82592:0f86b51f8f8b
>> user:Raymond Hettinger
>> date:
that changed. I prefer to use the term
"null merge" when I explicitly revert the code before committing, and
in this case I would have used "Merge with 3.x.".
FWIW I might add http://bugs.python.org/issue15917 at some point, to
prevent these situations.
Best Regards,
Ezi
scenario that doesn't really happen
often™[0] happened I can point to some actual graphs that will
hopefully clarify why all these merges are necessary :)
Best Regards,
Ezio Melotti
[0]: http://bugs.python.org/issue14468#msg184140
___
Python-Dev mailing
loaded TortoiseHg. Tomorrow I
> will re-clone and share the repository. Since this is the second time I have
> re-cloned from python.org, I will follow the advice I read somewhere to make
> a _backup clone that I leave alone until I need it, so I only have to pull
> from now until then
Hi,
On Tue, Mar 12, 2013 at 7:19 PM, Terry Reedy wrote:
> On 3/12/2013 2:52 AM, Ezio Melotti wrote:
>> What are the exact commands you used?
>
> Clicks on TortoiseHg HgWorkbench GUI ;-).
>
I wonder if TortoiseHg is doing something wrong here. Maybe you could
try from cmd
he problem is? Has anything changed with hg,
> windows, line endings and this text file in the last few months? I just
> pushed patches for about 20 scattered files in Docs, Lib, Modules, and Tools
> earlier today, so the problem seems to be specific to NEWS.
>
Not sure about this, but i
Hi,
On Mon, Mar 11, 2013 at 3:28 PM, Antoine Pitrou wrote:
> On Mon, 11 Mar 2013 08:14:24 +0100 (CET)
> ezio.melotti wrote:
>> http://hg.python.org/cpython/rev/da3f4774b939
>> changeset: 82600:da3f4774b939
>> branch: 2.7
>> parent: 82593:3e14aafeca0
itertools import islice as _islice
> +from collections import deque as _deque
>
Shouldn't the one in the 'try' be _islice too?
Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python
hased" free copy of Windows in my
e-cart, and some .exe I had to download in order to download and
verify the purchased copy. That's where I gave up.
Best Regards,
Ezio Melotti
> So it would appear that section "1.1.3.3. Windows" of "1. Getting Started"
> (setup.
; CLA is required.
>
http://psf.upfronthosting.co.za/roundup/meta/issue461
Best Regards,
Ezio Melotti
> --
> Terry Jan Reedy
>
___
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
ror: unexpected exception during garbage collection
Current thread 0x:
make: *** [pybuilddir.txt] Aborted (core dumped)
See also:
http://buildbot.python.org/all/builders/AMD64%20Fedora%20without%20threads%203.x/builds/4006
http://buildbot.python.org/all/builders/AMD6
ins word" [0][2].
Perl also has a similar-looking operator [3] (=~) used to test a regex match.
Best Regards,
Ezio Melotti
[0]: http://www.w3.org/TR/selectors/#selectors
[1]: http://api.jquery.com/attribute-starts-with-selector/
[2]: http://api.jquery.com/attribute-contains-word-selector/
[3
On Thu, Jan 24, 2013 at 4:29 AM, Chris Jerdonek
wrote:
> On Wed, Jan 23, 2013 at 6:16 PM, Ezio Melotti wrote:
>> On Wed, Jan 23, 2013 at 9:43 PM, Antoine Pitrou wrote:
>>> On Wed, 23 Jan 2013 20:41:11 +0100
>>> "Amaury Forgeot d'Arc" wrote:
>&
#12345 is now
fixed'.
With the new solution 1-2 work (the links are added/moved at the end),
but it's glitched for case 3.
Unless interhg provides a way to limit the replacement only to
specific places and/or use different replacements for different
places, we will either have to live w
on is
collecting stats about the patches available on the tracker. I put
together a temporary page that allows you to enter the name of a module (or
any file/path) and get a list of issues with patches that affect the
specified module(s): http://wolfprojects.altervista.org/issues.html
FTR this is based on the word done by anatoly (see links on the page).
I'm planning to eventually integrate this in the tracker too, but lately I
don't have too much time, so there's no ETA.
Best Regards,
Ezio Melotti
___
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
On Wed, Sep 26, 2012 at 6:02 PM, Walter Dörwald wrote:
> On 26.09.12 16:43, ezio.melotti wrote:
>
>> http://hg.python.org/cpython/rev/36f61661f71e
>> changeset: 79194:36f61661f71e
>> user:Ezio Melotti
>> date:Wed Sep 26 17:43:23 2012 +0300
>>
On Fri, Sep 14, 2012 at 2:22 AM, Chris Jerdonek
wrote:
> On Thu, Sep 13, 2012 at 4:00 PM, ezio.melotti
> wrote:
>> http://hg.python.org/cpython/rev/76dd082d332e
>> changeset: 79022:76dd082d332e
>> branch: 2.7
>> parent: 79014:8f847f66a49f
>>
dition, you might want to check the Roundup XML-RPC docs:
http://roundup.sourceforge.net/docs/xmlrpc.html
and the source of the script that generates the summary:
http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary
Best Regards,
Ezio Melotti
___
On Sun, Jul 22, 2012 at 12:18 PM, anatoly techtonik wrote:
> What is a print policy for deprecated modules? "new" module is
> deprecated in 2.6, but 2.7.3 doesn't print any warnings. Is it a bug?
> python -Wd -c "import new"
In theory this should show a warning, but for some reason it doesn't
useful if you want
HTMLParseErrors for an arbitrary subset of markup errors.
As someone already suggested, I should write a blog post explaining
all this, but I'm still working on ironing out the last things in the
code, so the blog post has yet to re
ython/devguide/peps/etc.) except that
no one ported it yet?
Best Regards,
Ezio Melotti
___
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/ar
ernal _names instead is a good idea at
this point. This will cause more breakage, and it would require an
extensive renaming. I can add notes to the documentation/docstrings and
specify what's private and what's not though.
OTOH, if this spe
3.rst
> @@ -23,7 +23,7 @@
> :file:`/tmp/example` file::
>
The filename here should be updated too.
> import sqlite3
> - conn = sqlite3.connect('/tmp/example')
> + conn = sqlite3.connect('example.db')
Best Regards,
Ezio Melotti
hed
> the Developer's Guide for both deprecation and DeprecationWarning and found
> nothing.
See http://mail.python.org/pipermail/python-dev/2011-October/114199.html
Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.or
Hi Ezio,
Am 02.03.2012 um 10:33 schrieb Ezio Melotti:
Reading this led me to think the following:
* 2.5 is now available basically everywhere, and it was released almost 5 years
ago (Sep 2006);
* if it takes the same time for 3.3, it will be widespread after 4-5 years
(i.e. 2016-2017) [0
ble somewhere? How difficult is the installation?
Does it strip the u automatically or is there a further step that
developers should do before testing on 3.1/3.2?
Best Regards,
Ezio Melotti
[0]: ISTM that people think "once you decide to switch to 3.x, there's
really no reason to
On 28/02/2012 18.08, Vinay Sajip wrote:
Ezio Melotti gmail.com> writes:
For every CPython bug that I fix I first apply the patch on 2.7, then on
3.2 and then on 3.3.
Most of the time I don't even need to change anything while applying the
patch to 3.2, sometimes I have to do some
;t need ugly hacks to work.
* in this case all the string literals I had were already text (rather
than bytes) and even without using unicode_literals they worked out of
the box when I moved the code to 3.x. There was however a place where
it didn't work, and that turned out to be a bu
On 18/02/2012 0.04, Nick Coghlan wrote:
On Fri, Feb 17, 2012 at 4:29 AM, Ezio Melotti wrote:
I'm assuming that eventually the module will be removed (maybe for Python
4?), and I don't expect nor want to seen it removed in the near future.
If something gets removed it should be deprec
On 16/02/2012 19.55, Antoine Pitrou wrote:
On Thu, 16 Feb 2012 19:32:24 +0200
Ezio Melotti wrote:
If I'm writing code that imports cElementTree on 3.3+, and I explicitly
turn on DeprecationWarnings (that would otherwise be silenced) to check
if I'm doing something wrong, I would like
hould the
other Python implementation have a to keep around a dummy module due to
a CPython implementation detail?
If we all go through a deprecation process we will eventually be able to
get rid of this.
Best Regards,
Ezio Melotti
Stefan
___
material make it clear to users which versions are normal feature
releases and which are LTS releases? How do we manage user
expectations?
This is not an issue with the scheme I proposed.
A community poll or survey to collect opinions from the greater Python
community would be valuable be
order of Misc/ACKS.
Best Regards,
Ezio Melotti
Eli
___
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
Eric.
And on the next line it should be 'persistent'.
Best Regards,
Ezio Melotti
___
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
Hi Éric,
On 31/10/2011 19.19, Éric Araujo wrote:
Hi Ezio,
http://hg.python.org/cpython/rev/18bbfed9aafa
user:Ezio Melotti
summary:
Add a button to the code examples in the doc to show/hide the prompts and
output.
Looks cool! I hope this will stop our use of two or three
this shortcut!
However I think I'll just leave $(document).ready(...); because, even if
longer, is more explicit and readable.
Best Regards,
Ezio Melotti
--Berker
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listi
n then link to it.
Best Regards,
Ezio Melotti
[0]: http://bugs.python.org/issue13248
[1]: deprecated-removed doesn't seem to be documented in the documenting
doc, but it was added here: http://hg.python.org/cpython/rev/03296316a892
[2]: see e.g.
http://hg.python.org/cpython/file/default/L
cidentally (an
"are you sure?" popup might solve this).
ctrl+enter/ctrl+s might be better, but they might conflict with the
browser commands.
* While replying (i.e. while writing in the comment textarea), the
shortcuts are disabled.
You can hit ESC to
Thu Sep 29 04:02:13 2011 +0200
summary: Fix hex_digit_to_int() prototype: expect Py_UCS4, not
Py_UNICODE
changeset: 72517:ba6ee5cc9ed6
user:Ezio Melotti
date:Thu Sep 29 08:34:36 2011 +0300
summary: Update and reorganize the whatsnew entry for PEP 393.
# here comes the tip: be
On 23/09/2011 20.11, Éric Araujo wrote:
Hi Victor,
diff --git a/Misc/NEWS b/Misc/NEWS
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -10,6 +10,10 @@
Core and Builtins
-
+- Issue #7732: Don't open a directory as a file anymore while importing a
+ module. Ignore the direcotry if its nam
unless_symlink", but the
other two skipUnless have more readable names: "requires_zlib" and
"requires_IEEE_754". In Lib/test/ "skipUnless" is used about 250 times,
"skipIf" about 100.
Best Regards,
Ezio Melotti
Michael
__
read != ch:
> raise AssertionError("%r != %r" % (read, ch))
>
Why not just assertEqual?
>
> -ch = ord('\xe9')
> +ch = ord('a')
> curses.unget_wch(ch)
> read = stdscr.get_wch()
> if read != ch:
>
>
>
Best Regards,
Ezi
it and have him review the result).
If making a diff with the current re is doable and makes sense, we can use
the rietveld instance on the bug tracker to make the review for 2). The
same could be done with a diff that replaces the whole module though.
3) will follow after 2), and 4) is not difficult
On Sat, Aug 27, 2011 at 4:56 AM, Antoine Pitrou wrote:
> On Sat, 27 Aug 2011 04:37:21 +0300
> Ezio Melotti wrote:
> >
> > I'm not sure it's worth doing an extensive review of the code, a better
> > approach might be to require extensive test coverage (and a
o many
incompatibilities left and if they can't be fixed in regex.
Best Regards,
Ezio Melotti
[0]: http://pypi.python.org/pypi/regex/0.1.20110717
[1]: "The NEW flag turns on the new behaviour of this module, which can
differ from that of the 're' module, such as splitting on
3.2?" thread (
http://mail.python.org/pipermail/python-dev/2010-July/101606.html ).
Best Regards,
Ezio Melotti
>
> --
> --Guido van Rossum (python.org/~guido <http://python.org/%7Eguido>)
>
___
Python-Dev mailing list
Python-Dev@p
ward
incompatible. In Python 2 UTF-8 can be used to encode every codepoint from
0 to 10, and it always works. If we change it now it might start
raising errors for an operation that never raised them before (see
http://bugs.python.org/issue12729#msg142047 ).
Luckily this is fixed in Python 3.x
icode strings are not limited to scalar values,
because they can also contain lone surrogates.
I hope this helps clarify the terminology a bit and doesn't add more
confusion, but if we want to use the Unicode terms we should get them
right. (Also note that I might have misunderstood somethin
ce the pointer [0] (and do it manually in the other functions like
is*) or change the function to get the original string too.
2) I'm on vacation.
Best Regards,
Ezio Melotti
[0]: for lower/upper/title it should be possible to modify the string in
place, because these operations never converts a non-
mError, but I'm only -0 for
FileSystemError (so I expect that will be the option chosen, given
other responses).
This pretty much summarizes my thoughts. I saw the wiki article using
both and since I consider 'filesystem' a single word I was wondering if
anyone else preferred Filesyst
we don't have the
'source' directive available in Sphinx and therefore we would have to
update all the links manually to link to h.p.o instead of s.p.o.
Best Regards,
Ezio Melotti
What do we use to provide the web part of hg.p.o? maybe we can just
ask the developers of this tool to pr
x27;s fine).
+ an absolute path for *host*, starting with a '/'.
Authentication is supported, using the regular SMTP mechanism. When using
a Unix
socket, LMTP generally don't support or require any authentication, but
your
diff --git a/Lib/smtplib.py b/Lib/smtplib.py
--
e same line, it returns None, and None is
assigned to *paths* -- and this seems wrong;
packagePathMap[packagename] = paths
Also this is not necessary anymore if you use setdefault.
replacePackageMap = {}
@@ -106,14 +102,14 @@
[...]
Best Regards,
Ezio Melotti
__
python/rev/c1a12a308c5b .
Before the change import_fresh_module was still returning the module
(e.g. json) even when the acceleration (fresh=['_json']) was missing,
and the C tests were run twice using the same pure-python module used
for the Py ones.
The typo and the wrong doc is al
1 - 100 of 132 matches
Mail list logo
