On Sun, 6 Aug 2017 03:18 am, Michael Torrie wrote:
> Forgive Steven for his off-topic reply. I assume he's trying to goad you
> into having a more specific subject line. He knows darn well what PyQt,
> even if he has no experience with it.
Pardon me, I said:
"I don't know what Qt signals are."
On 08/05/2017 05:36 PM, Ned Batchelder wrote:
> On 8/5/17 5:41 PM, Tim Daneliuk wrote:
>> On 08/05/2017 11:16 AM, Ned Batchelder wrote:
>>> It uses
>>> reference counting, so most objects are reclaimed immediately when their
>>> reference count goes to zero, such as at the end of local scopes.
>>
On 08/05/2017 05:36 PM, Ned Batchelder wrote:
> On 8/5/17 5:41 PM, Tim Daneliuk wrote:
>> On 08/05/2017 11:16 AM, Ned Batchelder wrote:
>>> It uses
>>> reference counting, so most objects are reclaimed immediately when their
>>> reference count goes to zero, such as at the end of local scopes.
>>
On 08/05/2017 05:58 PM, Chris Angelico wrote:
> On Sun, Aug 6, 2017 at 7:32 AM, Tim Daneliuk wrote:
>> On 08/05/2017 03:21 PM, Chris Angelico wrote:
>>> After a 'with' block,
>>> the object *still exists*, but it has been "exited" in some way
>>> (usually by closing/releasing an underlying resourc
On 08/05/2017 05:58 PM, Chris Angelico wrote:
> On Sun, Aug 6, 2017 at 7:32 AM, Tim Daneliuk wrote:
>> On 08/05/2017 03:21 PM, Chris Angelico wrote:
>>> After a 'with' block,
>>> the object *still exists*, but it has been "exited" in some way
>>> (usually by closing/releasing an underlying resourc
On Sun, Aug 6, 2017 at 7:32 AM, Tim Daneliuk wrote:
> On 08/05/2017 03:21 PM, Chris Angelico wrote:
>> After a 'with' block,
>> the object *still exists*, but it has been "exited" in some way
>> (usually by closing/releasing an underlying resource).
>
> The containing object exists, but the things
#I'm pleased to announce version 3.4.0, the first stable release of branch
#3.4 of SQLObject.
#
#
#What's new in SQLObject
#===
#
#* Python 2.6 is no longer supported. The minimal supported version is
# Python 2.7.
Is there a particular reason to eliminate RHEL 6 (Python 2.6)
On 8/5/17 5:41 PM, Tim Daneliuk wrote:
> On 08/05/2017 11:16 AM, Ned Batchelder wrote:
>> It uses
>> reference counting, so most objects are reclaimed immediately when their
>> reference count goes to zero, such as at the end of local scopes.
> Given this code:
>
> class SomeObject:
> .
>
On 2017-08-05 22:41, Tim Daneliuk wrote:
On 08/05/2017 11:16 AM, Ned Batchelder wrote:
It uses
reference counting, so most objects are reclaimed immediately when their
reference count goes to zero, such as at the end of local scopes.
Given this code:
class SomeObject:
.
for foo in
Tim Daneliuk :
> Are you saying that each time a,b,c are reassigned to new instances of
> SomeObject the old instance counts go to 0 and are immediately - as in
> synchronously, right now, on the spot - removed from memory?
That depends on the implementation of Python. CPython employs reference
c
On 08/05/2017 11:16 AM, Ned Batchelder wrote:
> It uses
> reference counting, so most objects are reclaimed immediately when their
> reference count goes to zero, such as at the end of local scopes.
Given this code:
class SomeObject:
.
for foo in somelist:
a = SomeObject(foo)
b
On 08/05/2017 03:21 PM, Chris Angelico wrote:
> After a 'with' block,
> the object *still exists*, but it has been "exited" in some way
> (usually by closing/releasing an underlying resource).
The containing object exists, but the things that the closing
logic explicitly released do not. In some
I had recently uploaded a package on pypi. For some reason, I removed the
package, and committed a BIG mistake along the way.
I clicked the DELETE PACKAGE [Warning about NEVER TO CLICK THAT BUTTON] (silly
me!)
Now, after re-uploading the package, its not visible on pypi.
How can I fix this? I alr
On Sun, Aug 6, 2017 at 1:23 AM, Tim Daneliuk wrote:
> On 08/04/2017 07:00 PM, Chris Angelico wrote:
>> Again, don't stress about exactly when objects get
>> disposed of; it doesn't matter.
>
>
> Respectfully, I disagree strongly. Objects get build on the heap and
> persist even when they go out o
On 08/05/2017 08:28 AM, veek wrote:
>
At a certain point beyond the general stuff, questions about PyQt might
be better suited to the PyQt mailing list, hosted by the company that
maintains PyQt:
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
--
https://mail.python.org/mailman/listi
On 08/05/2017 12:19 PM, Marko Rauhamaa wrote:
> I would express it as just saying that the Qt developers appropriated
> the word "signal" for what is simply a callback.
I'd say a slot is a callback. A signal is the designation of something
that will trigger callbacks.
> Years back I took a brief
Le 05/08/17 à 16:28, veek a écrit :
1. What exactly is a signal. In hardware, an interrupt can be viewed as a
signal and the voltage on a pin will suddenly jump to +5V as an indicator
that an interrupt has occurred. With Qt signals - if a widget-c++ code has
to 'signal' an event - what does it do
On 8/5/17 11:23 AM, Tim Daneliuk wrote:
> On 08/04/2017 07:00 PM, Chris Angelico wrote:
>> Again, don't stress about exactly when objects get
>> disposed of; it doesn't matter.
>
> Respectfully, I disagree strongly. Objects get build on the heap and
> persist even when they go out of scope until s
Yes. There is. I have been in need of this for a while until I found out. 2
steps:
- pip install pip-chill
- pip-chill
The list will only have what you directly installed and will not list
itself, which is pretty neat. The only thing you'll notice is that it's not
alphabetically arranged.
Cheers.
On 8/4/17 7:42 PM, Jon Forrest wrote:
> On 8/4/2017 4:34 PM, gst wrote:
>> 'two' is a so called constant or literal value .. (of that
>> function).
>>
>> Why not attach it, as a const value/object, to the function itself ?
>> So that a new string object has not to be created each time the
>> functi
Tim Daneliuk :
> On 08/04/2017 07:00 PM, Chris Angelico wrote:
>> Again, don't stress about exactly when objects get disposed of; it
>> doesn't matter.
>
> Respectfully, I disagree strongly. Objects get build on the heap and
> persist even when they go out of scope until such time garbage
> collec
Michael Torrie :
> Basically a signal emission is a call to the main loop that indicates
> that an event has occurred, and then the main loop sees if there are
> any registered callbacks that want to be notified of this event, and
> if so it calls them, letting them execute. This is how event-driv
Hello!
I'm pleased to announce version 3.4.0, the first stable release of branch
3.4 of SQLObject.
What's new in SQLObject
===
Contributor for this release is Dr. Neil Muller.
Features
* Python 2.6 is no longer supported. The minimal supported version is
Python
Forgive Steven for his off-topic reply. I assume he's trying to goad you
into having a more specific subject line. He knows darn well what PyQt,
even if he has no experience with it.
And of course, as always you will want to post a complete, working
example that we can see and comment on, rather
Steve D'Aprano wrote:
> On Sun, 6 Aug 2017 12:28 am, veek wrote:
>
>> 1. What exactly is a signal. In hardware, an interrupt can be viewed as a
>> signal and the voltage on a pin will suddenly jump to +5V as an indicator
>> that an interrupt has occurred. With Qt signals - if a widget-c++ code
>>
On 08/04/2017 07:00 PM, Chris Angelico wrote:
> Again, don't stress about exactly when objects get
> disposed of; it doesn't matter.
Respectfully, I disagree strongly. Objects get build on the heap and
persist even when they go out of scope until such time garbage
collection takes place. This i
On Sun, 6 Aug 2017 12:28 am, veek wrote:
> 1. What exactly is a signal. In hardware, an interrupt can be viewed as a
> signal and the voltage on a pin will suddenly jump to +5V as an indicator
> that an interrupt has occurred. With Qt signals - if a widget-c++ code has
> to 'signal' an event - wha
1. What exactly is a signal. In hardware, an interrupt can be viewed as a
signal and the voltage on a pin will suddenly jump to +5V as an indicator
that an interrupt has occurred. With Qt signals - if a widget-c++ code has
to 'signal' an event - what does it do?
As a consequence of not understa
On 08/05/2017 04:52 AM, Chris Green wrote:
> I went through a similar process of deciding the easiest (for me) GUI
> to go with. I've actually ended up with PyGtk as it feels for me the
> 'least foreign' compared with doing things the CLI way.
Yes PyGtk is fairly Pythonic and natural feeling. PyQ
On 8/5/2017 1:45 AM, Ulli Horlacher wrote:
Any kind of installer is not acceptable.
Is the requirement "no installer" or "single file" or both?
You can satisfy the "no installer" requirement also by just distributing
the .py file, the interpreter and a .bat file that e.g. contains
"python27\py
Michael Torrie wrote:
> On 08/04/2017 05:45 PM, Ulli Horlacher wrote:
> > I have to transfer a python 2.7 CLI programm into one with a (simple) GUI.
> > The program must run on Linux and Windows and must be compilable with
> > pyinstall, because I have to ship a standalone windows.exe
> > Any kind
On 8/5/2017 2:45 AM, Ulli Horlacher wrote:
I do not like GTK and Qt, because they are too complex.
I'm not a programmer, but at least simple cross platform GUI
notification message was easiest to do with PyQt (IMO).
--
https://mail.python.org/mailman/listinfo/python-list
Chris Angelico writes:
> 4503599761588224
I get the same result from searching a wider interval (+/- 50) around
each perfect square in the relevant range.
--
https://mail.python.org/mailman/listinfo/python-list
33 matches
Mail list logo
