Ian Kelly :
> On Jul 14, 2016 11:37 AM, "Marko Rauhamaa" wrote:
>> Where do you get the idea that the common usage is "wrong?" What do
>> you use as a standard?
>
> Is it "wrong" to consider some usages "wrong"? By what standard?
>
> I'm not interested in arguing over philosophy, so I won't.
Com
Steven D'Aprano writes:
> On Fri, 15 Jul 2016 09:13 am, Brendan Abel wrote:
> > since they all use software that is closed-source. At some point,
> > paying for software just makes sense.
Is it 1998 again already?
Or am I expecting too much that people involved in software in the 21st
century
On Friday, July 15, 2016 at 12:17:27 PM UTC+12, Ian wrote:
> Is it "wrong" to consider some usages "wrong"? By what standard?
Do you say “head over heels” or “heels over head”? “Burgle” or “burglari{s,z}e”?
--
https://mail.python.org/mailman/listinfo/python-list
On Fri, 15 Jul 2016 09:13 am, Brendan Abel wrote:
> In the article he makes a good point that if
> you're that worried about always using open-source, then you shouldn't be
> using gmail, or twitter, or even automobiles,
It's not a good point. I don't use gmail, or twitter, and if I could find a
On Fri, 15 Jul 2016 09:04 am, Lawrence D’Oliveiro wrote:
> On Friday, July 15, 2016 at 7:04:14 AM UTC+12, hasan...@gmail.com wrote:
>
>> ... I see nothing git offers over mercurial.
>
> Except greater productivity.
That has not been even close to my experience. And I don't mean my
*personal* ex
On Jul 14, 2016 11:37 AM, "Marko Rauhamaa" wrote:
>
> Ian Kelly :
> > On Thu, Jul 14, 2016 at 10:02 AM, Marko Rauhamaa
wrote:
> >>In American English, the original word for [significand] seems to
> >>have been mantissa (Burks[1] et al.), and this usage remains
> >>common in computing
On Friday, July 15, 2016 at 5:11:46 AM UTC+12, Ian wrote:
> Just because it's already common to use the wrong term doesn't mean
> the usage should be promulgated further.
Yes of course. The only logically-acceptable meaning of “mantissa” is “female
mantis”, and any other usage is to be the immedi
A lot of these arguments and points have already been made and hashed out
on the python-dev list. There's a very good article that one of the python
core developers wrote about the decision to move to github
http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-github
Basically,
On Friday, July 15, 2016 at 7:04:14 AM UTC+12, hasan...@gmail.com wrote:
> ... I see nothing git offers over mercurial.
Except greater productivity.
--
https://mail.python.org/mailman/listinfo/python-list
Appreciate it! Will do!
--
https://mail.python.org/mailman/listinfo/python-list
On 7/14/2016 3:04 PM, hasan.di...@gmail.com wrote:
Python's primary repository is Mercurial (hg.python.org), not Git.
CPython's current repository
Ditto for the PSF Python docs.
Were python to switch,
Like it or not, CPython and the Docs are moving to git and github.
PEPs and the devg
Michael Torrie writes:
>I understand that in Python's case, pure cost wins out. Python.org
>could host a GitLab instance, which contains the repo tools plus ticket
>tracking, etc, and ordinary developers could push their changes to their
>own public git repos and send in pull requests and it wou
Carter Temm wrote:
> Hi all.
> I've been looking at this for a bit, and can't seem to come to a possible
> conclusion on what could be happening to get an error. Anyway, here is the
> code, then I'll explain.
>
> http://pastebin.com/raw/YPiTfWbG
>
> the issue comes when using argv. But when I ch
Carter Temm wrote:
> Hi all.
> I've been looking at this for a bit, and can't seem to come to a possible
> conclusion on what could be happening to get an error. Anyway, here is the
> code, then I'll explain.
>
> http://pastebin.com/raw/YPiTfWbG
>
> the issue comes when using argv. But when I ch
On Thursday, July 14, 2016 at 10:39:35 AM UTC-7, Carter Temm wrote:
> Hi all.
> I've been looking at this for a bit, and can't seem to come to a possible
> conclusion on what could be happening to get an error. Anyway, here is the
> code, then I'll explain.
>
> http://pastebin.com/raw/YPiTfWbG
>
Ian Kelly :
> On Thu, Jul 14, 2016 at 10:02 AM, Marko Rauhamaa wrote:
>>In American English, the original word for [significand] seems to
>>have been mantissa (Burks[1] et al.), and this usage remains
>>common in computing and among computer scientists. >https://en.wikipedia.org/wi
Hi all.
I've been looking at this for a bit, and can't seem to come to a possible
conclusion on what could be happening to get an error. Anyway, here is the
code, then I'll explain.
http://pastebin.com/raw/YPiTfWbG
the issue comes when using argv. But when I change
TIME = argv
to
TIME = 2
I
On Thu, Jul 14, 2016 at 10:02 AM, Marko Rauhamaa wrote:
> Ian Kelly :
>
>> The significand of -3.14159 is the sequence of digits 314159. The
>> mantissa of -3.14159 is the number 0.85841.
>
> Fight it all you want. However:
>
>In American English, the original word for [significand] seems to
>
Ian Kelly :
> The significand of -3.14159 is the sequence of digits 314159. The
> mantissa of -3.14159 is the number 0.85841.
Fight it all you want. However:
In American English, the original word for [significand] seems to
have been mantissa (Burks[1] et al.), and this usage remains commo
On 2016-07-14 15:30, Ian Kelly wrote:
On Jul 14, 2016 1:52 AM, "Steven D'Aprano"
wrote:
On Thursday 14 July 2016 15:18, Ian Kelly wrote:
Side note, neither do floating point numbers, really; what is often
called the mantissa is more properly known as the significand. But
integers don't have
On Jul 14, 2016 1:52 AM, "Steven D'Aprano"
wrote:
>
> On Thursday 14 July 2016 15:18, Ian Kelly wrote:
>
> > Side note, neither do floating point numbers, really; what is often
> > called the mantissa is more properly known as the significand. But
> > integers don't have that either.
>
>
> Er, the
#!/usr/bin/python
import logging
logging.getLogger("scapy.runtime").setLevel(logging.ERROR)
from scapy.all import TCP, IP, ICMP, sniff
def ip_callback(pkt):
print '--- IP--'
pkt.show()
print 'IP', pkt.src, pkt.sport, '--->', pkt.dst, pkt
For this year, we have reconsidered the way we give out badges to try
to reduce the queue lengths and your waiting time.
Badges distributed based on ticket ID
-
To make finding badges easier, we have printed the ticket ID on each
badge and will distribute badg
On Thu, Jul 14, 2016 at 6:16 PM, Steven D'Aprano
wrote:
> How about some really random data?
>
> py> import string
> py> data = ''.join(random.choice(string.ascii_letters) for i in range(21000))
> py> len(codecs.encode(data, 'bz2'))
> 15220
>
> That's actually better than I expected: it's found so
Steven D'Aprano wrote:
> How about some really random data?
>
> py> import string
> py> data = ''.join(random.choice(string.ascii_letters) for i in
> range(21000)) py> len(codecs.encode(data, 'bz2'))
> 15220
>
> That's actually better than I expected: it's found some redundancy and
> saved about
On July 14, 2016 2:59:09 AM GMT+05:30, vineeth menneni
wrote:
>Hi I am finding it difficult to create a excel sheet using openpyxl or
>xlsxwriter. The problem is that i am loading a table data from MYSQL db
>which has 600k rows and 15 columns (approximately 100mb data). The
>error that the term
I thought I'd experiment with some of Python's compression utilities. First I
thought I'd try compressing some extremely non-random data:
py> import codecs
py> data = "something non-random."*1000
py> len(data)
21000
py> len(codecs.encode(data, 'bz2'))
93
py> len(codecs.encode(data, 'zip'))
99
On Thursday 14 July 2016 15:18, Ian Kelly wrote:
> Side note, neither do floating point numbers, really; what is often
> called the mantissa is more properly known as the significand. But
> integers don't have that either.
Er, then what's a mantissa if it's not what people call a float's mantiss
On Thursday 14 July 2016 10:14, Ian Kelly wrote:
> On Wed, Jul 13, 2016 at 12:48 PM, Vijay Kumar
> wrote:
>> Hi Everyone,
>> I wrote an article on Python byte code hacking. The article is available
>> from http://www.bravegnu.org/blog/python-byte-code-hacks.html The article
>> uses an incremental
29 matches
Mail list logo
