#pyqt | Logs for 2019-01-10

Back
[00:52:54] <altendky> russw: back down to a reasonable file size and the qml example runs... https://ci.appveyor.com though it looks like i'm missing a lot more than the d.dll and .pdb that i meant to. :|
[01:08:35] -!- mandeep has quit [Remote host closed the connection]
[03:05:47] -!- Mrokii has quit [Ping timeout: 240 seconds]
[03:20:19] -!- BPL has joined #pyqt
[03:45:31] -!- kallesbar has joined #pyqt
[04:16:01] -!- russw has quit [Ping timeout: 268 seconds]
[06:12:17] -!- anqxyr has joined #pyqt
[09:10:37] -!- Siecje has joined #pyqt
[09:29:14] -!- kallesbar has quit [Quit: Konversation terminated!]
[09:42:36] -!- kallesbar has joined #pyqt
[09:54:09] -!- anqxyr has quit [Read error: Connection reset by peer]
[10:25:40] -!- russw has joined #pyqt
[10:47:44] -!- AbleBacon has joined #pyqt
[10:55:15] -!- nitro25 has joined #pyqt
[10:58:30] -!- agile_prg has joined #pyqt
[11:05:36] -!- nitro25 has quit [Remote host closed the connection]
[11:06:26] -!- nitro25 has joined #pyqt
[13:00:56] <russw> altendky: have you tried using your `pyqt5*.exe` executables as run configurations in Qt Creator? The env fiddling may be useful in that case, so I'm curious if that was part of the origin for making them.
[13:02:13] <altendky> russw: no. i use designer and the plugin. my widgets for my dash are mostly custom. i could certainly add a pyqt5creator (well, is creator in pyqt5-tools right now?)
[13:02:31] <russw> not what I meant...
[13:02:40] <altendky> oh sorry...
[13:02:43] <altendky> hmm
[13:02:50] <russw> Qt Creator lets you spec out different run configurations for projects.
[13:02:54] <altendky> the answer is still no :] but..
[13:02:55] <russw> i.e. what happens when you click run
[13:03:00] <russw> I gathered that :)
[13:03:02] <altendky> right, i just misread
[13:03:38] <altendky> russw: along with reducing file size, i did add the usecwd=True
[13:03:44] <russw> My goal is getting qmltestrunner to work properly from QtCreator... taking some tinkering and I don't want to have static env vars
[13:03:51] <russw> nice
[13:03:55] <russw> I'll try that later for sure
[13:04:10] <altendky> yeah, if there's something else i can add, i'm happy to consider it
[13:04:37] <altendky> russw: did you want to make up example and automated test qml files? or should i plan on figuring that out.
[13:05:09] <russw> altendky: I'd like to help on that, but it won't be this week or next
[13:05:24] <russw> trying to get this dev environment working has already taken WAY more time than I wanted
[13:05:52] <altendky> russw: yeah, every time i touch this mess it does
[13:06:06] <russw> it feels like a frigging dumpster fire
[13:06:15] <altendky> and i'm still not convinced it's all working everywhere... but maybe with some of the stuff you pointed out we're closer
[13:06:44] <russw> once it is set up my hope is that it the pain is just a past/solved problem
[13:07:24] -!- BPL has quit [Read error: Connection reset by peer]
[13:08:00] -!- BPL has joined #pyqt
[13:08:04] <altendky> russw: if at any particular point you want something on pypi rather than appveyor, let me know. it's a tag+push+wait-a-few-hours-for-the-build away (though i'd do an rc or something at this point)
[13:08:30] <russw> anything that isn't stable right now?
[13:08:55] <russw> i.e. why hold back on bumping the version now?
[13:09:18] <altendky> russw: i dunno. like i said i felt like my file filtering pulled out a lot more than it was supposed to. and that chart demo is probably not a very complete test :|
[13:09:19] <russw> I guess tests and the other stuff you mentioned
[13:09:24] <altendky> russw: i'd like to put in tests anyways for the qml
[13:09:27] <altendky> yeah
[13:09:42] <altendky> and maybe even reduce the shotgun path approach. but probably realistically not
[13:10:05] <russw> I really think that os.path.dirname(sys.executable) should work
[13:10:18] <russw> ... btu I have a faint memory that you needed something else as well
[13:11:08] <russw> no, I'm dumb
[13:11:17] <altendky> russw: yeah, i thought i tried just that. i mean there's a whole DLLs subdirectory in the main python install
[13:11:21] <russw> there was more because of the virtualenv pain I had
[13:11:45] <altendky> and getting the main system stuff even when you are in the env, not just the env directory
[13:11:51] <altendky> env scripts directory
[13:12:35] <altendky> i assume it'll frustrate someone running qmlscene and having this polluted path, but ... enh
[13:13:09] <russw> maybe not, since it is only getting polluted when you've already decided which pyqt5*.exe you want to run
[13:13:26] <russw> the DLL import path seems unlikely to cause an issue...
[13:13:37] <russw> and 640k RAM is all anyone will ever need
[13:13:41] <russw> so you never know
[13:14:28] <altendky> well, maybe we update it to nobody will ever need more than 640k IoT devices... that might hold for a year or two
[13:16:35] <russw> given that most IoT devices probably run massively bloated OS+software on them, I'd bet that'd blown already :)
[13:17:11] <russw> (yes I recognize the irony of saying that on #pyqt, which is a freaking *huge* bloated pile, all considered)
[13:17:14] <altendky> russw: oh, absolutely. i meant literally 640 thousand IoT devices per person
[13:17:58] <russw> mandatory and somewhat-related xkcd:
[13:17:58] <russw> https://xkcd.com
[13:18:50] <altendky> heh
[13:19:23] <altendky> i don't actually follow xkcd so the links are actually new to me (other than the regular repeats in #python)
[14:53:01] -!- kallesbar has quit [Quit: Konversation terminated!]
[15:06:54] -!- BPL has quit [Read error: Connection reset by peer]
[15:07:43] -!- BPL has joined #pyqt
[15:59:52] -!- nitro25 has quit [Remote host closed the connection]
[16:02:52] -!- mintograde has joined #pyqt
[16:59:04] -!- russw has quit [Ping timeout: 250 seconds]
[17:03:31] -!- Siecje has parted #pyqt
[18:11:36] -!- AbleBacon has quit [Quit: Leaving]
[19:15:00] -!- russw has joined #pyqt
[19:20:59] -!- daegontaven has joined #pyqt
[20:11:31] -!- BPL has quit [Quit: Leaving]
[21:15:21] -!- daegontaven has quit [Quit: Leaving]
[21:56:40] -!- mintograde has quit [Ping timeout: 272 seconds]