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
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
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
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
.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
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
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
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
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
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
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
>>
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
"/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
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
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
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
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/
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,
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
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,
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
://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
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).
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.
>>>
>>
>> +
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
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 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
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
__
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
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
; 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
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.
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
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
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 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
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
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
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
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:
+
> +.. _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
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
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
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
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
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
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/
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
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
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
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
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
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
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
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
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
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
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
Python currently accepts global statements at the top level:
global foo
Beside being a meaningless operation, this might lead unexperienced
user to make mistakes like:
foo = 5
global foo # make foo global
def func():
... print foo # access the global foo
...
func()
5
# it works!
"glob
I noticed that in the py3k doc 'mktemp' is marked as deprecated since
Python 2.3 [1], but the function is still there and doesn't raise any
warning. Looking at the source I found out that there is a warning, but
it is commented out [2], the reason being because they are "too annoying".
There was
On 28/01/2010 8.39, Brett Cannon wrote:
On Wed, Jan 27, 2010 at 15:54, Ezio Melotti wrote:
I noticed that in the py3k doc 'mktemp' is marked as deprecated since Python
2.3 [1], but the function is still there and doesn't raise any warning.
Looking at the source I found out
In #7712 I was trying to change regrtest to always run the tests in a
temporary CWD (e.g. /tmp/@test_1234_cwd/).
The patches attached to the issue add a context manager that changes the
CWD, and it works fine when I run ./python -m test.regrtest from trunk/.
However, when I try from trunk/Lib/ i
On 23/03/2010 16.50, Brian Curtin wrote:
Hi all,
Having been active in bug triage and patch writing/reviewing since
late 2009, it was suggested in the python-dev IRC channel that I
request commit access to the repository. I'm primarily a Windows user
and have worked with many of the other act
Hi,
now that the py3k warnings are fixed (see
http://bugs.python.org/issue7092) we should run the tests on the trunk
buildbots with the -3 flags, in order to check if new warnings are
introduced and possibly to uncover other ones.
It might be a good idea to add the -Wd flag too, both on trunk
On Tue, Apr 27, 2010 at 5:16 PM, Barry Warsaw wrote:
> On Apr 27, 2010, at 02:40 PM, exar...@twistedmatrix.com wrote:
>
> >On 01:38 pm, rdmur...@bitdance.com wrote:
>
> >>2) have unit tests that fail before the patch and succeed after
> >
> >This list would make a good addition to one of the
lotti".
Otherwise we can just decide that those names should just be added to
the nosy list and let them assign the issue to themselves if they want
to fix it.
Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@pytho
On 01/08/2010 20.43, R. David Murray wrote:
On Sun, 01 Aug 2010 21:28:05 +1000, Nick Coghlan wrote:
On Sun, Aug 1, 2010 at 5:41 PM, Mark Lawrence wrote:
I plucked this figure out of the air thinking that if an issue was going to
drop under the radar, this would be the most likely time. I was
d:`site` module
-
___
Python-checkins mailing list
python-check...@python.org
http://mail.python.org/mailman/listinfo/python-checkins
Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
ekly summary and mail them
to python-dev, but someone should write some code (I could do that but
it's quite low in my to-do list) and make it run once a week.
Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
valid_sigs[cur_sig]);
+if (!valid_sig) {
+PyErr_SetString(PyExc_ValueError, "signal number out of range");
+return NULL;
+}
+#endif
#ifdef WITH_THREAD
if (PyThread_get_thread_ident() != main_thread) {
PyErr_SetString(PyExc_ValueError,
_
xml.etree import ElementTree as ET
SIMPLE_XMLFILE = findfile("simple.xml", subdir="xmltestdata")
+try:
+ SIMPLE_XMLFILE.encode("utf8")
+except UnicodeEncodeError:
+raise unittest.SkipTest("filename is not encodable to utf8")
SIMPLE_NS_XMLFILE = fi
e to
be closed, rather than for how long the open issues are around.
For more information see
http://psf.upfronthosting.co.za/roundup/meta/issue284.
Best Regards,
Ezio Melotti
P.S.: Thanks to R. David Murray that helped me out with the testing and
to all the people who provided (and wil
On 11/08/2010 17.59, Mark Dickinson wrote:
On Wed, Aug 11, 2010 at 3:21 PM, Tim Golden wrote:
Thanks to whoever's been working on the new Summary lists on the Issue
Tracker.
Ezio Melotti, I assume.
Yes :)
(see http://psf.upfronthosting.co.za/roundup/meta/issue329)
The "Follo
)
closed 19597 (+78)
total 22111 (+95)
as suggested in recent mails[0][1] I changed these values to represent
the deltas with the previous week.
Now let's try to keep the "open" delta negative ;)
Best Regards,
Ezio Melotti
[0]: http://mail.python.org/pipermail/python-dev/2010-Octo
On 06/11/2010 19.01, Terry Reedy wrote:
On 11/6/2010 11:42 AM, R. David Murray wrote:
On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl
wrote:
Am 06.11.2010 05:44, schrieb Ezio Melotti:
Hi,
On 05/11/2010 19.08, Python tracker wrote:
ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
Python tracker
e
>>> b'\x80abc'.decode("utf-8", "replace")
-'\ufffdabc'
+'�abc'
Apparently 'make latex' and 'make all-pdf' don't like this char.
>>> b'\x80abc'.decode("utf-8&q
are passed to
python.
If no flags are passed the default will be -Wd, otherwise the behavior
will be the one specified by the flag.
This will allow developers to use `python -Wi` to ignore errors explicitly.
Best Regards,
Ezio Melotti
___
Python-De
On 22/11/2010 19.45, Michael Foord wrote:
On 22/11/2010 17:35, Łukasz Langa wrote:
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently
we have a horde
On Fri, Jan 7, 2011 at 4:39 PM, phillip.eby wrote:
> Author: phillip.eby
> Date: Fri Jan 7 16:39:27 2011
> New Revision: 87815
>
> Log:
> More bytes I/O fixes
>
>
> Modified:
> peps/trunk/pep-.txt
>
> Modified: peps/trunk/pep-.txt
>
>
(http://code.google.com/p/bbreport/wiki/Screenshots):
hg clone https://bbreport.googlecode.com/hg/ bbreport
cd bbreport
python bbreport --help
python bbreport 3.x
(There is some issue with hg revision numbers that I haven't fixed yet,
but the above command should work fine)
Best Regards,
Ezio Melotti
On 11/03/2011 4.45, Nick Coghlan wrote:
On Thu, Mar 10, 2011 at 4:36 PM, ezio.melotti
wrote:
http://hg.python.org/cpython/rev/9adc4792db9a
changeset: 68356:9adc4792db9a
branch: 2.7
user:Ezio Melotti
date:Thu Mar 10 23:35:39 2011 +0200
summary:
Use simpler assert in
rging 3
branches rather than 2 doesn't make much difference with mercurial.
[0]: http://bugs.python.org/issue2650
[1]: http://hg.python.org/cpython/rev/1402c719b7cf
[2]: http://hg.python.org/cpython/rev/9147f7ed75b3
[3]: http://hg.python.org/cpython/rev/ed02db9921ac
Best Regards,
Ezio Melotti
On 30/03/2011 23.20, Antoine Pitrou wrote:
On Tue, 29 Mar 2011 21:00:22 +0200
ezio.melotti wrote:
http://hg.python.org/devguide/rev/f722956afeac
changeset: 405:f722956afeac
user:Ezio Melotti
date:Tue Mar 29 22:00:13 2011 +0300
summary:
Add a table of contents to the FAQ
e some patches ready that just need to
be updated and applied.
In the meanwhile you can use
http://wiki.python.org/moin/DesiredTrackerFeatures to list the things
that you would like to see, so that they don't get lost in the archives
of python-dev.
Best Regards,
Ezio Melotti
o put
roundup in bottom-post (chronological) format?
TIA!
~Ethan~
See line 309 of
http://svn.python.org/view/tracker/instances/python-dev/html/issue.item.html?view=markup
If you have other questions about Roundup see
https://lists.sourceforge.net/lists/listinfo/roundup-users
Best Regards,
If(sys.platform == 'darwin'
- and platform.mac_ver()[0].startswith('10.4.'),
- 'Mac OS X Tiger log2() is not accurate enough')
def testLog2Exact(self):
+# log2() is not accurate enough on Mac OS X Tiger (10.4)
+
est one and use it on all the
branches.
See also http://bugs.python.org/issue5587
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/mai
Hi,
On 14/07/2011 15.57, ezio.melotti wrote:
http://hg.python.org/cpython/rev/ac1c3291a689
changeset: 71325:ac1c3291a689
parent: 71321:f45823977d4b
parent: 71324:530ba6c7e578
user:Ezio Melotti
date:Thu Jul 14 15:57:12 2011 +0300
summary
lmost) impossible.
Messages and files can be deleted/restored from their pages. Links to
these pages can be found in the history of the issue. For messages and
files that are still linked to the issue, the "(view)" and "edit" links
can also be used.
Best Regards,
Ezi
(http://docs.python.org/documenting/markup.html#information-units)
Best Regards,
Ezio Melotti
> 2. Some functions like unlink and rmtree are obviously
redundant, and shadow
> frequently used Python stdlib funct
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
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
__
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
--
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
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
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-
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
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
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
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
1 - 100 of 132 matches
Mail list logo
