Senthil Kumaran orsent...@gmail.com added the comment:
Fixed in r85347 and r85348.
--
nosy: +orsenthil
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment:
Yes, but http://docs.python.org/genindex-Z.html
ZipFile (class in zipfile), [1]
still has same issue, no? [1] (and [2], [3], if exist)
should suggest alternatives, but it doesn't now.
I'll attach the patch to detect this kind
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment:
Daniel, we need to sync-up on the meaning of marking a report as
accepted. Traditionally it denotes an approved patch, not a agreement
that the bug is valid.
Woops! Thanks for the correction. For what it's worth, a
Akira Kitada akit...@gmail.com added the comment:
Forgot to mention that there's no _MAX macro for exact-width integer types.
$ egrep -r 'INT[0-9].*_MAX' /usr/include/ | wc -l
0
How about adding those macros when the system does not provide them?
--
New submission from eswar s eswar...@yahoo.com:
-5 ** 4 results as -625. It should be 625
--
components: None
messages: 118311
nosy: eswar.s
priority: normal
severity: normal
status: open
title: ** operator yielding wrong result for negative numbers
type: compile error
versions: Python
Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment:
Umm, I tried, but I couldn't post new issue with error.
I believe Sphinx guys also look at this tracker.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10008
Senthil Kumaran orsent...@gmail.com added the comment:
It's to do with operator precedence.
** takes higher precedence than negative.
http://docs.python.org/reference/expressions.html#Summary
(-5) ** 4 will give what you are looking for.
--
nosy: +orsenthil
resolution: - invalid
Changes by Ned Deily n...@acm.org:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10054
___
___
Python-bugs-list mailing list
Raymond Hettinger rhettin...@users.sourceforge.net added the comment:
Please pass the word along if you get a chance :-)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10029
___
New submission from Akira Kitada akit...@gmail.com:
Build fails on FreeBSD 4 due to the lack of sem_timedwait.
gcc -pthread -Wl,--export-dynamic -o python Modules/python.o libpython3.2.a
-lutil -lm
libpython3.2.a(thread.o): In function `PyThread_acquire_lock_timed':
Antoine Pitrou pit...@free.fr added the comment:
What happens if you comment out # define USE_SEMAPHORES in
Python/thread_pthread.h?
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10062
Akira Kitada akit...@gmail.com added the comment:
It works fine with USE_SEMAPHORES commented out.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10062
___
Antoine Pitrou pit...@free.fr added the comment:
What about this patch?
Index: Python/thread_pthread.h
===
--- Python/thread_pthread.h (révision 85348)
+++ Python/thread_pthread.h (copie de travail)
@@ -64,7 +64,8 @@
/*
Antoine Pitrou pit...@free.fr added the comment:
3.1 branch does not have this problem because that patch was not
applied to release31-maint. Is this intentional?
I don't remember, I suppose it feared it could be an incompatible change or
perhaps cause build problems.
Anyway, I committed
Akira Kitada akit...@gmail.com added the comment:
The patch does fix the build error.
Thank you!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10062
___
Antoine Pitrou pit...@free.fr added the comment:
Patch committed in r85352, thanks.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10062
Brian Brazil brian.bra...@gmail.com added the comment:
That doesn't cover the os.path.join('', 'x') case, and I'm not sure it makes
os.path.join('x//', 'y') clear - though that doesn't matter as much.
How about making (2) the result is simply path2 when path1 is empty or path2
is an absolute
Georg Brandl ge...@python.org added the comment:
This can be solved after 3.2a3.
--
assignee: - ronaldoussoren
nosy: +georg.brandl, ronaldoussoren
priority: release blocker - deferred blocker
___
Python tracker rep...@bugs.python.org
Georg Brandl ge...@python.org added the comment:
Deferring once again.
--
priority: release blocker - deferred blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8611
___
Stefan Krah stefan-use...@bytereef.org added the comment:
FreeBSD 5.0 has stdint.h, which includes machine/_stdint.h. In the
latter file the *_MAX constants are defined.
It looks like FreeBSD has had the correct setup for more than 7 years:
Antoine Pitrou pit...@free.fr added the comment:
Committed to 3.x in r85353.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9437
___
___
New submission from Senthil Kumaran orsent...@gmail.com:
file:// scheme should not be allowed to access a file on remote machines. RFC
1738, says that host, if present should be the FQDN of the machine, but
relaxing on that I thinking that localhost and its variants should okay as long
as it
kiorky kio...@cryptelium.net added the comment:
We must not have the same point of view about new features and bugfixes...
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1777412
___
Antoine Pitrou pit...@free.fr added the comment:
Backported to 2.7 in r85358.
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9437
Akira Kitada akit...@gmail.com added the comment:
I understand FreeBSD 4.x is old platform (4.11, the last 4.x series, is
released 5 years ago) but, in my opinion, as long as it does not make Python
code cluttered, supporting old platforms is not that bad idea.
Anyway, I would like to leave
Martin v. Löwis mar...@v.loewis.de added the comment:
kiorky: see my msg55157. Python behaves correctly as it stands - raising the
exception is fully intentional. It's not a bug that it gets raised; dates
before 1900 are just not supported. Adding support for them is a new feature.
--
Stefan Krah stefan-use...@bytereef.org added the comment:
r85358 fixes the failures in test_sysconfig. The duplicate LDFLAGS are
still present, but if it is generally accepted that make-LDFLAGS should
be appended to configure-LDFLAGS, then I don't see any way around that.
As for me, this could
Simon Liedtke liedtke.si...@googlemail.com added the comment:
I see that adding this method to a deque is useless. A list is better for this
kind of operation. I just wrote it for fun and realized that it was implemented
rather slow.
--
resolution: - rejected
status: open - closed
New submission from anatoly techtonik techto...@gmail.com:
Link to bugtracker on http://docs.python.org/dev/bugs.html leads to main
roundup page. It make more sense to redirect to a page that lists only
documentation bugs.
Extra points:
- sort the landing page that Easy, then issues with
R. David Murray rdmur...@bitdance.com added the comment:
Does it also need a deprecation cycle?
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10063
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
We run into problems because we have two inconsistent
encodings, ...
What? No. We have problems because we don't use the same encoding to decode and
to encode the same data type. It's not a problem to use a different encoding
Martin v. Löwis mar...@v.loewis.de added the comment:
Am 10.10.2010 17:51, schrieb STINNER Victor:
STINNER Victor victor.stin...@haypocalc.com added the comment:
We run into problems because we have two inconsistent encodings,
...
What? No. We have problems because we don't use the
MunSic JEONG rus...@gmail.com added the comment:
Do you have a patch to fix the issue?
no, I don't. I just wanted to move stage from unittest needed to needs
patch :)
After reading issue8098, now I realized that this is broad issue as belopolsky
said in msg110095.
For new reader of this
STINNER Victor victor.stin...@haypocalc.com added the comment:
What? No. We have problems because we don't use the same encoding to
decode and to encode the same data type. It's not a problem to use a
different encoding for each data type (stdout, filenames, environment
variables, ...).
Martin v. Löwis mar...@v.loewis.de added the comment:
For the command line arguments and environment variables, we don't have a lot
of choices: locale or filesystem encodings. So Antoine and Martin: which
encoding do you prefer?
I still propose to drop the fsname encoding. Then this
Antoine Pitrou pit...@free.fr added the comment:
Le dimanche 10 octobre 2010 à 18:23 +, Martin v. Löwis a écrit :
Martin v. Löwis mar...@v.loewis.de added the comment:
For the command line arguments and environment variables, we don't have a
lot
of choices: locale or filesystem
Raymond Hettinger rhettin...@users.sourceforge.net added the comment:
Python's order of operations runs the exponentation before the unary minus.
This convention makes the unary minus behave more like the subtraction operator
so that: -x**n == 0 - x**n.
This convention is somewhat common
New submission from Andreas Stührk andy-pyt...@hammerhartes.de:
Title says all, attached is a patch against release27-maint that adds them.
--
assignee: d...@python
components: Documentation
files: future_builtins_docstring.patch
keywords: patch
messages: 118343
nosy: Trundle,
Martin v. Löwis mar...@v.loewis.de added the comment:
I don't know what you mean by dropping, since OS X by construction needs
a filesystem encoding (utf-8) different from the locale encoding;
See above. I propose to stop using the locale encoding for command line
arguments and environment
Terry J. Reedy tjre...@udel.edu added the comment:
When I initially wrote I have no idea what ', [1]' is supposed to mean.
, you should have believed that and explained ;-). I now understand that most
index entries have one link, which we might call the [0] link. When the entry
should have
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Partial fix checked into py3k and release27-maint branches (for losing filename
case information) - r85361.
Regarding performance changes - awaiting feedback from Armin re. my performance
measurements showing only marginal differences.
Changes by Matthew Woodcraft matt...@woodcraft.me.uk:
--
nosy: +mattheww
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4106
___
___
42 matches
Mail list logo
