« first day (10 days earlier)      last day (203 days later) » 

00:02
RELOAD!
[Cardshifter/Cardshifter] 5 commits. 3 opened issues. 1 closed issue. 4 issue comments.
[retailcoder/Rubberduck] 15 commits. 5 opened issues. 1 closed issue. 6 issue comments.
[ShearOfDoom/Cactus] 23 commits. 11 opened issues. 10 closed issues. 53 issue comments.
[Vannevelj/VSDiagnostics] 1 commit. 1 opened issue. 1 issue comment.
 
1 hour later…
01:03
> Issue fixed. The only thing you have to do is put the @cactus_class_method_exception_handle decorator over each classmethod.
[ShearOfDoom/Cactus] ShearOfDoom pushed commit df408eab to master: Fixed issues with errors.py
01:31
Hey, @AnnonomusPenguin, nicely formatted errors!
[ShearOfDoom/Cactus] ShearOfDoom pushed commit 3e91015d to master: Added some special error trace formatting.
[ShearOfDoom/Cactus] ShearOfDoom pushed commit 85f5e46c to master: Fixed indentation errors.
01:56
Hello @Doorknob
02:11
IT'S TOO QUIET
02:24
@Doorknob was in here?
The Doorknob?
I think
I saw his profile picture in the collection of user profile pictures.
@AnnonomusPenguin btw, I've implemented the error handling system. It uses function decorators.
in The 2nd Monitor, 2 mins ago, by Ethan Bierlein
Hello @JonSkeet
02:45
Ok. So no exceptions?
Essentially, it'll print the entire stacktrace to a file, along with other useful info.
02:59
Hello
?
03:09
03:47
Any list of previous commands @EthanBierlein?
@AnnonomusPenguin I'm not sure what you mean...
I implemented the error handling. Essentially, each function is decorated with an error handler that'll log errors to the file.
 
1 hour later…
05:13
Night
 
9 hours later…
14:37
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit 32da4886 to master: Please use PEP 8, as always
@Ethan the error handling is really cool!
15:00
I'm adding a few things to the data so things can better be diagnosed and reproduced
15:16
@AnnonomusPenguin Thanks! I actually learned how Python decorators work just for that purpose. xD
@EthanBierlein haha
Also, what would the new error reports look like?
I'm just adding more info, like Python version, etc.
System architecture, blarg
Also: I'm giving the full file path to the user if they don't know where the error reports are stored
15:18
Ah, okay. The file should be in the same directory as their game file.
Wouldn't it be in the cactus folder?
Nope. Tested it last night. It'll be in the same directory as the user's game file.
Ah, that kinda makes sense.
But, at the same time... nope!
Technical users might know where to look, but the average game-player won't.
Hmm. Well. Okay. Even if it is in the same dir, the path will still be useful.
If someone makes a real game out of this, they might add an installer or something more detailed
Or package it into a binary file (you can do that with Python, right?)
15:25
I think, I'm not sure. There is a python module called py2exe which converts Python files to executables.
We could have py2exe packaged in as long as the license isn't wonky like pyfiglet.
Later :p
Not yet
See ya
Scratch that, there is a version for Python3.
@EthanBierlein I meant add that later
I'm not leaving
Oh, okay.
15:46
> Python: CPython v3.4.3:9b73f1c3e601 Feb 24 2015 22:43:06 MSC v.1600 32 bit (Intel)
^^^ Needs moar pYthon information
> Operating System: Windows-8-6.2.9200
> Processor: AMD64 Family 21 Model 1 Stepping 2, AuthenticAMD
> Default Browser (to tell if you should help this person or not): Chrome
16:58
@AnnonomusPenguin The variables in TEST_test1.py are capitalized because they remain constant.
17:13
[ShearOfDoom/Cactus] ShearOfDoom pushed commit e1a8433c to master: Changed wording to not imply that every error is dev-related.
@EthanBierlein ehh, don't they change? Internally?
That's not constant
And why don't you have class_data_keys_types a constant, then?
Ooh, I'll fix that right now.
brb
@Ethan I just realized this: why do you use nested lists for class_data_keys_types?
Why not a dictionary?
Hmm... would that work?
No idea.
I'll see if I can refactor that after I rename those variables.
It seems like it'd be simpler
@Ethan re: github.com/ShearOfDoom/Cactus/commit/…: I did it that way so they knew that 1.) they didn't do something wrong 2.) they wouldn't be asked to submit a Cactus bug report when the developer should be the one submitting it 3.) wouldn't be asking us for support for a developer's bug
I was thinking that the game developer could contact us themselves, and give us more helpful information than the average player
17:25
Ah, okay, I'll revert that.
But you're right
I think that we should change that so it doesn't put blame on the developer
Something like this?:
Oh, okay.
> Something wrong internally happened (not your fault!). This may be an issue with the game itself, or the underlying components. To help fix this issue, please contact the developers of the game with the error report in this location:
What about that?
Can you do that? I don't have time right now (or I can do it myself later)
17:27
Yup.
Also, RE: github.com/ShearOfDoom/Cactus/commit/…: I'm confused on if this is a constant or not. The class doesn't mutate itself, but it mutates the internal components
I see both sides of the issue rn and am not sure
@EthanBierlein thanks!
To the user, the data doesn't change, so those variables should be constant.
Hmm... but with the error handler
They could mutate the GAME_MAP or something in an event handler
Hmm, true.
Oh well, for now, let's just keep them as constants.
I think by constants that they mean literal stuff like PI = 3.14
@EthanBierlein ok
I'm actually really excited with this error-handling thing. It's a cool feature that we might want to advertise ("gracefully generates error logs when exceptions thrown, and gracefully notifies the user to send in the error report")
Wordsmithing required ^^^
17:33
You are our master wordsmith. :D
[ShearOfDoom/Cactus] ShearOfDoom pushed commit 8b1a6e12 to master: Refactored naming, and some wording.
YAY 80 COMMITS
@EthanBierlein nah :D
That's a nice round number.
100 will be better though.
tempted to push commit to make a one-letter change
17:42
Oh, where?
git commit -m "Added newline at end of file to make it 81 commits"
We haven't had any starts recently
17:43
@Phrancis Starred us yesterday
I meant in chat
The first day every other message was starred. Now it's like one in 80
18:07
@AnnonomusPenguin Now every other one is starred.
 
3 hours later…
20:45
@EthanBierlein oh great
21:12
@AnnonomusPenguin What happened?
@EthanBierlein not sure if you are curious to play my new game, but i just uploaded it to pixelpocalypse.com/voxelcity
21:36
@EthanBierlein check which message I replied to :)
Frankly, I'm wonder what happened, myself.
22:20
Wow, it only took github a minute to sync all the changes to my dev laptop.
 
1 hour later…
23:21
Good Morning @all
23:38
Hello @Quill

« first day (10 days earlier)      last day (203 days later) »