Steffen Daode Nurpmeso added the comment:
Salut!, amis français! (Und auch sonst so, natürlich.)
POSIX has recently standardized a NSIG_MAX constant in limits.h [1]:
The value of {NSIG_MAX} shall be no greater than the number of signals that
the sigset_t type (see [cross-ref to signal.h
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
R. David Murray wrote [2012-03-17 03:51+0100]:
Thanks for the patch, Steffen.
Warm wink to the cleanroom-squatters!
(I count this as the promised petit glass of red wine.)
--steffen
Forza Figa
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Let me close this!
I've just recently removed the real patch from my postman's next
branch, because even that real implementation doesn't work reliable.
I.e., please forget msg135791. It was true, but on the long run
mutt(1
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Closing this...
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11686
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I think this is historic either?
As far as i remember you solved it as part of another issue...
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Right, and that is considered to be a non-issue due to
that close() is allowed multiple times without causing harm.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
--
nosy: -sdaoden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11466
___
___
Python
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Heya.
OpenBSD does support 1:1 threads via the RThread library
since 2005, thanks to tedu@ and more fantastic guys!
It about to be super-stable (one commit in 2011, last real
fix in april 2010).
(There is a techtalk from tedu@ (Ted
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
In Python 3.3, you can use sys.thread_info to check which threading
library is used.
Great! I didn't know that!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
A sign!
A sign!
Someone with a name-name-name!!
(Not a useful comment, i'm afraid.)
--
nosy: +sdaoden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12730
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
--
nosy: -sdaoden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12730
___
___
Python
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Are you willing to update your patch accordingly?
I'm a vain rooster! I've used fullfsync() in 11877-standalone.1.diff!
Sorry for that, haypo. :-/
11877.fullsync-1.diff uses fullsync() and will instead always be
provided when
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Even PEP 3151 won't help.
I don't understand. If the syscall supposed to flush the disk's buffer
cache fails - be it fcntl() or sync_file_range() - I think the error
should be propagated, not silently ignored and replaced
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Here is something unsorted and loose:
- @neologix:
One could argue that something had happened before the fsync(2),
so that code which blindly did so is too dumb to do any right
decision anyway. Even PEP 3151 won't help
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
If Nir's analysis is right, and Antoines comment pushes me into
this direction, (i personally have not looked at that code),
then multiprocessing is completely brain-damaged and has been
implemented by a moron.
And yes, I know
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Um, and just to add: i'm not watching out for anything, and it won't
and it can't be me:
?0%0[steffen@sherwood sys]$ grep -F smp CHANGELOG.svn -B3 | grep -E
'^r[[:digit:]]+' | tail -n 1
r162 | steffen | 2006-01-18 18:29:58 +0100
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
P.S.:
I have to apologize, it's Tomaž, not Thomas.
(And unless i'm mistaken this is pronounced TomAsch rather than
the english Tommes, so i was just plain wrong.)
--Steffen
Ciao, sdaoden(*)(gmail.com)
() ascii ribbon campaign
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
then multiprocessing is completely brain-damaged and has been
implemented by a moron.
Please do not use this kind of language.
Being disrespectful to other people hurts the discussion.
So i apologize once again.
'Still i
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
So sorry that i'm stressing this, hopefully it's the final message.
Apples iterative kernel-update strategy resulted in these versions:
14:02 ~/tmp $ /usr/sbin/sysctl kern.version
kern.version: Darwin Kernel Version 10.8.0
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file22281/11277.apple-fix-2.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11277
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
My suggestion to this would be that it should be outdated in the
same way that Georg Brandl has suggested for changing the default
encoding on python-dev [1], and add clear documentation on that,
also in respect to the transition
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
How do you think multiprocessing.Process launches a new process?
But it's a single piece of code under control and even
multi-OS/multi-architecture test-coverage, not a general purpose
Joe, you may just go that way and Python
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Hello Valery Masiutsin, i recently stumbled over this while searching
for the link to the standart i've stored in another issue.
(Without being logged in, say.)
The de-facto standart (http://qmail.org/man/man5/mbox.html) says:
HOW
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ Ronald Oussoren wrote:
if major = 10:
# We're on OSX 10.6 or earlier
enableWorkaround()
(You sound as if you participate in an interesting audiophonic
event. 27 imac's are indeed great recording studio
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Ok, this patch could be used.
*Unless* the code is not protected by the GIL.
- Gestalt usage is a bit more complicated according to
http://www.cocoadev.com/index.pl?DeterminingOSVersion
unless Python only supports OS X
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file22273/11277.apple-fix.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11277
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Aehm, note that Apple has fixed the mmap(2) bug!!
I'm still surprised and can't really believe it, but it's true!
Just in case you're interested, i'll apply an updated patch.
Maybe Ned Deily should have a look at the version check
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ Ned Deily rep...@bugs.python.org wrote (2011-06-07 19:43+0200):
Thanks for the update. Since the fix will be in a future
version of OS X 10.7 Lion, and which has not been released yet,
so it is not appropriate to change mmap
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Hello, David, i'm about to remind you that this issue is still
open (and the next release is about to come soon).
I think we do agree at least in the fact that this is a bug :).
Well, your mailbox_close_twice.patch no. 2 still
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file22095/11700.yeah-review.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11700
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
that doesn't make me any good
Well - 'can only be better than myself, so i'll take that as yes :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12102
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file22020/12102.1.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12102
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
diff --git a/Doc/library/os.rst b/Doc/library/os.rst
--- a/Doc/library/os.rst
+++ b/Doc/library/os.rst
@@ -810,6 +810,35 @@
Availability: Unix, and Windows.
+.. function:: fullfsync(fd)
+
+ The POSIX standart requires
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
(This was an attachment to an empty mail message.)
--
Added file: http://bugs.python.org/file22046/11877-standalone.1.diff
___
Python tracker rep...@bugs.python.org
http
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Looked at it again and i think it's much better english with an
additional ..to ensure that local...
@Ross, aren't you a native english speaker? What do you say?
--
Added file: http://bugs.python.org/file22048/12102.2
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Excusing myself seems to be the only probates Mittel.
@Antoine Pitrou: It was a real shame to read your mail.
(It's sometimes so loud that i don't even hear what i write.)
--
___
Python
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ rion wrote (2011-05-18 12:39+0200):
just document it or fix.
Hello, zion, Victor, i'm proposing a documentation patch.
It applies to 2.7 and 3.3 (from yesterday).
--
keywords: +patch
Added file: http://bugs.python.org
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ STINNER Victor wrote (2011-05-18 14:33+0200):
I don't think that Python should guess what the user expects
(i.e. Python should not sync the file *implicitly*).
Before i've found F_FULLFSYNC i indeed have had a solution which
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ Nir Aides wrote (2011-05-16 20:57+0200):
Steffen, can you explain in layman's terms?
I am the layman here.
Charles-François has written a patch for Python which contradicted
his own proposal from msg135079, but he seems to have
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Thank you, thank you, thank you.
I'm a bit irritated that a french man treats a wet-her as a typo!
What if *i* like it?? In fact it is a fantastic physical backing
store. Unbeatable.
Well and about dropping the fsync() in case
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I've dropped wet-her!
I hope now you're satisfied!
So the buffer cache is all which remains hot.
How deserted!
And you could also add a test (I guess that just calling fsync
with full_sync=True on a valid FD would be enough
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21986/11877.8.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11877
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Finally, depending on the workload, it could have a significant
performance impact.
Oh yes (first replaces os.fsync() with an in-python wrapper):
18:12 ~/tmp $ ll mail
ls: mail: No such file or directory
18:12 ~/tmp $ ll X-MAIL
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ Charles-François Natali wrote (2011-05-15 01:14+0200):
So if we really wanted to be safe, the only solution would be to
forbid fork() in a multi-threaded program.
Since it's not really a reasonable option
But now - why
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@ Charles-François Natali rep...@bugs.python.org wrote (2011-05-13
13:24+0200):
I happily posted a reinit patch
I must say in advance that we have implemented our own thread
support 2003-2005 and i'm thus lucky not to need
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Just adding more notes on that by reactivating one of haypo's
links from #8604. (And: maybe some Linux documentation should be
updated?) From Theodore Ts'o,
http://www.linuxfoundation.org/news-media/blogs/browse/2009/03/don’t
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Dunno.
The patch is not completely safe.
Yeah it will not work without atomic ops.
Unfortunately the C standart seems to go into a direction
noone understands - as if a atomic_compare_and_swap() would
not suffice! Do you know
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On my Linux box, Python 3.3 says that signal.NSIG is equal to 65
which looks correct.
On FreeBSD NSIG only counts old signals (32, one 32 bit mask),
SIGRTMIN is 65 and SIGRTMAX is 126.
Our internal old signal.h states
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
[.]
OSError: [Errno 22] Invalid argument
Sorry, i didn't know that. Mac OS X (2.5 and 2.6 Apple shipped):
21:43 ~/tmp $ python2.5 -c 'import os; os.fsync(1)'; echo $?
0
21:43 ~/tmp $ python2.6 -c 'import os; os.fsync(1)'; echo
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
So I think you should stick with the previous version (well, if the
full sync fails on other FDs, then it's another story, but in that
case it should just be dropped altogether if it's not reliable...).
Strong stuff
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21973/11877.7.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11877
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@Nir Aides: *thanks* for this link:
http://groups.google.com/group/comp.programming.threads/msg/3a43122820983fde
You made my day!
--
nosy: +sdaoden
___
Python tracker rep
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
For the record:
On Mac OS X 10.6.7, ,HFS, case sensitive` updates st_atime by
itself *once only*. It does so ~0.75 seconds after os.utime() (+)
was called. A time.sleep(0.8) can be used to detect this automatic
update reliably
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Ouch, ouch, ouch!!
I'll have to send 11877.7.diff which extends 11877.6.diff.
This is necessary because using fcntl(2) with F_FULLFSYNC may fail
with ENOTTY (inapprobiate ioctl for device) in situations where
a normal fsync(2
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21924/11877.5.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11877
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21953/11877.6.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11877
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I don't agree with you and i don't believe it is implemented like
that. But it seems i am the only one on this issue who sees it
like that. Thus i apply 11877.6.diff.
Declaring variables as auto is not necessary in C code
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Ronald Oussoren wrote (2011-05-08 10:33+0200):
Steffen, I don't understand your comment about auto. Declaring
variables as auto is not necessary in C code and not used
anywhere else in Python's source code.
Well, as long as i
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@Nadeem: note that the committed versions of the tests would not
show up the Mac OS X mmap() bug AFAIK, because there is an
intermediate .close() of the file to be mmapped. The OS X bug is
that the VMS/VFS interaction fails
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
(Of course this may also be intentional, say.
But then i would vote against it :), because it's better the
tests bring out errors than end-user apps.)
--
___
Python tracker rep
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
That's really a good one.
(In my eyes.)
--
title: sporadic failure in test_mailbox - sporadic failure in test_mailbox on
FreeBSD
___
Python tracker rep...@bugs.python.org
http
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Sat, 7 May 2011 14:20:51 +0200, Charles-François Natali wrote:
I really can't see a good reason for using it here (and
anywhere, see http://c-faq.com/decl/auto.html).
You're right.
Why are you using the auto storage class
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Sat, 7 May 2011 14:20:51 +0200, Charles-François Natali wrote:
# ifdef __APPLE__
res = fcntl(fd, F_FULLFSYNC);
# endif
# ifdef __NetBSD__
res = fsync_range(fd, FFILESYNC|FDISKSYNC, 0, 0);
# endif
Since
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
This tracker - sorry!
(I surely will try to write and offer a patch for the tracker,
but first i need to understand that mailbox.py jungle for
#11935, next week.)
--
title: sporadic failure in test_mailbox on FreeBSD
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
11877.5.diff incorporates all changes suggested by
Charles-François except for the 'auto' keyword, which is extremely
important and which would need to be invented if it would not
yet exist.
I'm dropping the old stuff. And i
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21749/11877.3.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11877
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21771/11877.4.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11877
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Fri, 6 May 2011 04:44:00 +0200, R. David Murray wrote:
[.] the mtime only has a resolution of one second.
You always say that! But i'm pretty sure from somewhen long ago
that there are filesystems which have a two second
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I also added an additional delta in case the file system clock
is skewing relative to the system clock.
In fact this idea could even be made public e.g. like this
class ClockDrifter:
def add_snapshot(self, exttime
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I like all kind of single-screw solutions.
And i feel a bit uncomfortable with your usual tightness.
(0.1 seconds - i mean, come on)
--
___
Python tracker rep...@bugs.python.org
http
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
how many people are going to use maildir on FAT?
Dunno.
But it's maybe the lowest common denominator of mountable
readwrite filesystems. Except for that MacBook i always had
a shared FAT partition on my private PCs
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@david: note i got stuck on updating my patch for mailbox.py and
switched to do test_mmap.py instead, so that i don't know wether
i will be able to finish it today. Is it really true that
mailbox.py even writes mailboxes without
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I agree that it's fun to see pieces of code interacting like gears
in a transmission, but often it gets ugly due to the noise from
the outside which requires to add ugly fuzziness or honour stupid
design decisions.
Maybe
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Fri, 6 May 2011 02:54:07 +0200, Nadeem Vawda wrote:
I think so. [.]
it turns out that the OS X sparsefile crash is also covered by
LargeMmapTests.test_large_offset() in test_mmap [!!!]. [.]
So i followed your suggestion
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21869/11277-27.2.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11277
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21885/11277-27.3.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11277
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Thu, 5 May 2011 03:52:29 +0200, R. David Murray wrote:
[..] the shell [..] I believe it just looks at the mtime/atime.
/* check_mail () is useful for more than just checking mail. Since it has
the paranoids dream ability
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Thu, 5 May 2011 03:52:29 +0200, R. David Murray wrote:
[..] the shell [..] I believe it just looks at the mtime/atime.
Pretty good, huh?
Mr. Mojo says:
Prowd to be a part of this number.
Successful hills are here
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@haypo: trouble, trouble on the dev-list, as i've seen currently.
Sorry, sorry. (Cannot subscribe, my DynIP's are often blacklisted ;)
Of course my comments were completely wrong, as Ethan has pointed
out correctly.
This is all s
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
P.S.: if you're really right ('have those RFC's, but didn't read
them yet), you could also open an issue for Mercurial at
http://mercurial.selenic.com/bts - i think those guys do the very
same.
Thanks, Steffen!
--
nosy
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Thu, 5 May 2011 13:42:29 +0200, R. David Murray wrote:
what does mutt do in the case you are talking about?
16 -rwxr-s--- 1 steffen mail 14832 23 Jan 19:13 usr/bin/mutt_bitlock
set bitlock_program=~/usr/bin
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
The problem report in question was submitted by one of the
Debian maintainers.
Yeah, a documentainer at least.
I've used Debian (Woody i think that was 3.1).
Actually great because Lehmanns, Heidelberg, Germany did not
include
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
After half an hour of shallow inspection.
mutt really modifies mailbox files in place (mbox_sync_mailbox())
after creating (all the new tail in) a temporary file. Then
seek()/write()/truncate() etc.. It however has mutt_dotlock
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
In fact i like my idea of using iterations.
I have some time tomorrow, so if nobody complains until then,
i write diffs for the tests of 3.x and 2.7 with these updates:
- Two different target sizes:
1. 0x + x (7)
2
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Issue #11935 becomes gigantic and may even swamp this one over!
--
nosy: +sdaoden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7359
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Thu, 5 May 2011 19:04:16 +0200, R. David Murray wrote:
prepare new tail means all of the text from the first modified
line to the end? (As opposed to just the new mail?) mailbox
does locking. I see no reason in principle
New submission from Steffen Daode Nurpmeso sdao...@googlemail.com:
Yes, i really found a typo.
I'll send two patches, one with the typo fixed,
and one with the typo fixed and one for which
i've :setlocal tw=80:{gq}
--
assignee: docs@python
components: Documentation
messages: 135107
nosy
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
11997.1.diff only corrects the typo, 11997.2.diff does also
reformat. (Note that all of init.rst is hard to read on a 80
column terminal.)
--
keywords: +patch
Added file: http://bugs.python.org/file21880/11997.1.diff
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I think this relates #6896.
Maybe a two second resolution should be tried?
--
keywords: +patch
nosy: +sdaoden
Added file: http://bugs.python.org/file21884/11999.1.diff
___
Python
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
error: [Errno 12] Cannot allocate memory
@haypo: Well i told you i have no idea. These bots are 32 bit?
I'll attach 11277-27.3.diff which does @skipUnless(not 32 bit).
Note i'll test against _4G - does this work (on 32 bit
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
@haypo: Oh. Not:
if sys.maxsize _4G:
# (64 bits system) crc32() and adler32() stores the buffer size into an
# int, the maximum filesize is INT_MAX (0x7FFF)
filesize = 0x7FFF
crc_res
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Now me.
(http://gcc.gnu.org/onlinedocs/gcc/Arrays-and-pointers-implementation.html#Arrays-and-pointers-implementation)
When casting from pointer to integer and back again, the resulting
pointer must reference the same object
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Should we fix Python 2.7?
- backport issue #8651
- use PY_SSIZE_T_CLEAN in zlibmodule.c
I really thought about this over night.
I'm a C programmer and thus:
- Produce no bugs
- If you've produced a bug, fix it at once
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21855/11277-27.1.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11277
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
Ha! I always knew it! wink
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10276
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Sun, 1 May 2011 00:15:11 +0200, R. David Murray rep...@bugs.python.org
wrote:
The problem with this patch is that it would also show 'new
mail' if what had in fact happened was that a message had been
*deleted* (see
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
I'll attach a patch with a clearer comment (entry-gate instead
new mail), i.e. the comment now reflects what MUAs really do.
--
Added file: http://bugs.python.org/file21850/11935.2.diff
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21795/mailbox.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11935
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment:
On Mon, 2 May 2011 01:22:41 +0200, STINNER Victor rep...@bugs.python.org
wrote:
@sdaoden: Can you try on Python 2.7?
@haypo: Python 2.7 is absolute horror.
But i tried and produced a (terrible - i don't know the test
framework
Changes by Steffen Daode Nurpmeso sdao...@googlemail.com:
Removed file: http://bugs.python.org/file21673/11277.zsum32.c
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11277
1 - 100 of 368 matches
Mail list logo
