Then it doesn't matter, if you never distribute or sell it.
On Sat, 14 Mar 2015 11:01 AM Marcus Ottosson wrote:
> What I am talking about is a bundled application.
>
> But what I’m talking about is using it within a company, sorry for the
> confusion.
>
>
> --
> You received this message becau
What I am talking about is a bundled application.
But what I’m talking about is using it within a company, sorry for the
confusion.
--
You received this message because you are subscribed to the Google Groups
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and sto
Other interesting read:
http://blog.devork.be/2009/11/python-modules-and-gpl-i-still-dont-get.html
Shows just how complicated it is to actually understand it, since it
doesn't map cleanly to every circumstance. You can read some people say
that importing a GPL module makes your application depende
I don't really feel comfortable enough to argue about licenses, but I feel
part of what you say is the same as what I know about it. You can write an
application that requires PyQt4, and only distribute your original
application, with the caveat that the end user must install their own PyQt
to sati
Had a read through my reply and realised that it was quite rude, apologies!
Hope it didn't affect what little information I tried getting across. :)
--
You received this message because you are subscribed to the Google Groups
"Python Programming for Autodesk Maya" group.
To unsubscribe from thi
Software licenses are generally a magical mystery to me
Maybe you should have stopped there, because..
It makes your own source also need to be GPL and that you need to make your
source code available.
..this is not true in any regard.
I’ve spent significant time and effort into investigating v
Software licenses are generally a magical mystery to me, and there are
smart lawyers that are paid to fully understand them... but from what I
comprehend about GPL is that it is an "infectuos" type of license. It makes
your own source also need to be GPL and that you need to make your source
code a
Doesn’t change the license scheme.
I’ve heard that some refrain from using GPL, but I never understood why.
Its free so long as you don’t distribute the PyQt binaries *and don’t
include the source*. Distributing *with* the source is GPL compatible.
Either way, your company might restrict you from
Compiling is only part of it. Doesn't change the license scheme.
On Fri, 13 Mar 2015 7:41 AM Marcus Ottosson wrote:
> I’m pulling for it, because the licensing meant I could dream of a world
> where we wouldn’t have to keep compiling PyQt
>
> It’s a small world, after all, and it only takes one
I’m pulling for it, because the licensing meant I could dream of a world
where we wouldn’t have to keep compiling PyQt
It’s a small world, after all, and it only takes one of us to compile and
then share it with the rest.
Here’s my contribution.
https://github.com/pyqt
It could use some help; it
Third - we're basically taking the same approach for the moment, where we
import everything through an abstraction module, which can grab PySide or
PyQt as needed.
Longer term - yeah, I'm definitely worried about the health of PySide. I'm
pulling for it, because the licensing meant I could dream
I second what Justin said.
// F
tors 12 mar 2015 kl. 07:20 skrev Justin Israel :
> That would depend on your company, and whether your code is purely
> internal or if you ship code. For my company, in particular, it shouldn't
> matter since we handle it all internally with dependency management
That would depend on your company, and whether your code is purely internal
or if you ship code. For my company, in particular, it shouldn't matter
since we handle it all internally with dependency management. I have some
products that are only PySide but it would be trivial to adjust their
imports
How important it is to still support PyQt in your opinion? Would dropping
it entirely and focusing on PySide have any draw back in the long run?
On Thursday, March 12, 2015 at 1:29:59 AM UTC+7, Justin Israel wrote:
>
> That is pretty much all the information that I am aware of, as well.
> PySid
I personally avoid the UI files, but I know a lot of people like them.
On Wed, Mar 11, 2015 at 3:24 PM, Justin Israel
wrote:
> Or even better, avoid UI files altogether, if you can manage.
>
> On Thu, 12 Mar 2015 7:47 AM Fredrik Averpil
> wrote:
>
>> We've invested (so to speak) heavily in PySi
Or even better, avoid UI files altogether, if you can manage.
On Thu, 12 Mar 2015 7:47 AM Fredrik Averpil
wrote:
> We've invested (so to speak) heavily in PySide. But like Justin mentions
> the differences aren't that big between PySide/PyQt.
>
> However I'd like to point one thing out:
>
> If y
We've invested (so to speak) heavily in PySide. But like Justin mentions
the differences aren't that big between PySide/PyQt.
However I'd like to point one thing out:
If you are reading in external ui files, I would recommend defining a
routine/policy on how you do that throughout your company's
That is pretty much all the information that I am aware of, as well. PySide
was an easier choice for a while because of the distribution. It also had
more bugs and less development.
In terms of writing an app, it isn't actually too hard to write it to
dynamically handle supporting both PySide and P
To add some information on these topics I mentioned, I find this thread
really interesting. Confusing, though...
http://community.thefoundry.co.uk/discussion/topic.aspx?f=190&t=103100
--
Lidia
2015-03-11 16:27 GMT+01:00 darkgaze :
> Hello fellow programmers,
>
> once again, i dig up an old topi
19 matches
Mail list logo
