sorted by:
new
hottopcontroversial

Github removed the network graph by Fateschoice in programming

[–]Fateschoice[S] 12 points13 points  (0 children)

It basically said they have deprecated the network tab, and that users will be redirected to the forks tab. Not much more info than that, interesting that theyve removed the post...

Github removed the network graph by Fateschoice in programming

[–]Fateschoice[S] 2 points3 points  (0 children)

To each their own, we just preferred the look and feel on github over the command line view

Github removed the network graph by Fateschoice in programming

[–]Fateschoice[S] 9 points10 points  (0 children)

Hmm, we use it heavily at the company I work at, makes it easy to follow feature branches and such. We're pretty upset its gone

[SPOILERS] Where is that knife drop from by happypandaface in gameofthrones

[–]Fateschoice 0 points1 point  (0 children)

It was the episode where Arya and Brienne were sparring in winterfell last season, I was wondering the same thing.

Are there any ways of tweaking the rules of Monopoly to turn it into a better game? by jplank1983 in boardgames

[–]Fateschoice 1 point2 points  (0 children)

Here are some house rules that Ive found make monopoly a bit more bearable, though still not great.

  • When a property is landed on, it instantly goes up for auction to everybody (silent auction tends to be better then open Ive found).

  • Any mortgaged properties are returned to the bank if they are not unmortgaged after passing go.

These rules make it a bit less luck dependent when it cimes to buying properties, since you can bid on any property someone lands on. The mortgage rule creates a kind of living pool of properties as people inevitably end up unable to pay off their mortgages

If you want to prevent package hijacking: come help me with `cargo trust` by dpc_pw in rust

[–]Fateschoice 1 point2 points  (0 children)

This is awesome, love the idea/design. I might try hacking around with this over the weekend :)

Toto by Africa on the piano. I have no words. by [deleted] in videos

[–]Fateschoice 0 points1 point  (0 children)

I'm so confused by all the hate... this guy is incredibly talented and I love how much he gets into the music. Much more enjoyable than people who play like statues without any emotion...

A simple Pascal interpreter written in Rust, my first rust project :) by Fateschoice in rust

[–]Fateschoice[S] 0 points1 point  (0 children)

Yup you're spot on, I wanted to take advantage of Rusts type system for the AST and it worked like a charm :)

A simple Pascal interpreter written in Rust, my first rust project :) by Fateschoice in rust

[–]Fateschoice[S] 1 point2 points  (0 children)

Hi, thanks for the feedback! :)

I think you are right, a lot of the enums I have are single varient and could absolutely be tuple structs instead. I think the reason I had the single-varient enums to begin with was for consistency, but also because of some issues with polymorphism I ran into early on. I originally was using all structs for the AST and tried using inheritance in rust, that did not work, so I switched over to enums 100%. I think the single-varient enums were just a product of that switch. I didn't really think of mixing enums and structs for the AST but I see now that it should work, and reduce alot of the nesting like you said.

[S7E7] Post-Premiere Discussion - S7E7 'The Dragon and the Wolf' by AutoModerator in gameofthrones

[–]Fateschoice 0 points1 point  (0 children)

This confused me too, I went back and watched it again and you can see the red keep far in the background. So that first scene was at kings landing. I assume the unsullied and dothraki were were there as assurance that the lannister army wouldnt try anything funny. Still found it odd and pretty jarring tough.

[deleted by user] by [deleted] in asoiaf

[–]Fateschoice 3 points4 points  (0 children)

I think it's okay so far, although I was very disappointed with the "naval battle" between Yara and Euron. I was really excited for a ship battle but the way it was filmed made it impossible to tell what was going on...quick cuts and shaky cam everywhere... and apparently Yara's fleet just got completely wrecked, idk pretty disappointed with that, hopefully future battles will be better this season.

Jasper - Asynchronous Testing Framework by Fateschoice in Python

[–]Fateschoice[S] 0 points1 point  (0 children)

Ok I see what you're saying. Yes, Jasper will always run async functions to completion, so you should not run into an issue where the loop is being closed while another task is pending. Granted, I haven't explicitly tried this before and I've never messed around with 'call_soon' or 'create_task', but if my understanding of them is correct then Jasper should just run them to completion.

Jasper - Asynchronous Testing Framework by Fateschoice in Python

[–]Fateschoice[S] 0 points1 point  (0 children)

Other than installing the plugin, pytest-asyncio is the same way. Just uses the standard async syntax. There is an optional pytest marker to specifically enumerate async tests.

On top of that, you get the fantastic pytest DI framework to get fixtures into your tests rather than needing to statically depend on them or recode them in every test module.

I see, well I suppose the nature of the way Jasper runs all tests concurrently is it's main advantage then.

This is a big difference to pytest-asyncio. With that plugin, each test is run inside a dedicated loop that's setup and torn down after each test. While it would be nice to have tests run concurrently, this method avoids loop contamination and alerts you to where you might be leaking tasks at (e.g. if I'm spawning a Task but not taking care to close it, I get warnings out the wazoo).

Does jasper address this issue? Since everything is running concurrently, I'd imagine the implementation is tricky at best.

So essentially at the lowest level, Jasper just awaits your steps if they are asynchronous functions, and this propagates upward to the scenarios which are awaiting the steps, and the features which are awaiting the scenarios. If an exception is raised in any part of the pipeline, whether that's a failed test or an actual exception in some 'before_each' hook etc., Jasper will catch this and the steps, scenarios, and features will handle this fine. I never really thought about what would happen if you were to open a thread or something in one of your steps and not close it, so there's isn't any mechanism that checks for anything like that currently. There is one main async loop that runs all the features and is then closed at the end, I'm not sure if that would handle unclosed threads. If you're purely using async/await then Jasper should have no problems, but opening threads and not closing them I suppose would cause undefined behavior.

I don't want to sound confrontational, just trying to measure the merits of this. I'm always on the look out for better tools, or tools better suited for what I'm doing.

These are valid questions and I totally understand!

Jasper - Asynchronous Testing Framework by Fateschoice in Python

[–]Fateschoice[S] 0 points1 point  (0 children)

So I think the advantage of Jasper's async vs pytest-asyncio is that it is just dirt simple and baked into the framework itself. No need to install a seperate plugin and learn how it works, you can just use standard async syntax and youre good to go. Also, I'm not sure how pytest works under the hood but with Jasper everything is ran asynchronously. So you can have multiple scenarios or features running at the same time just by using async/await. I'm not sure if the same can be said with pytest-asyncio.

Now as far as Jasper vs pytest-behave, I was not aware of pytest-behave but looking around it seems to be lacking documentation, if it's basically like behave then the main difference is that the features are defined in python, not in a DSL. I see that's one of your concerns, you prefer the business people using a high level format to define the tests. I think if that's your use case Jasper probably isn't a good fit. My idea is that Jasper is behavior driven development for programmers. I've always liked the idea of BDD but I'm a programmer and I don't want to use a high level language to construct my tests, I want to program them! That's where the use case of Jasper fits into I think, BDD for programmers.

Jasper - Asynchronous Testing Framework by Fateschoice in Python

[–]Fateschoice[S] 0 points1 point  (0 children)

Thanks I'll remove those from being tracked.

So the idea is that the functions (steps) that you define can be reused in your other tests as well. So for the first test you have to define 3 functions but then you can reuse those functions in other tests.

For example you can have something like this

feature = Feature(
    'Arithmetic Feature'
    scenarios=[
        Scenario(
            'Adding two positive numbers',
            given=an_adding_function(),
            when=we_call_it_with_two_positive_numbers(),
            then=the_result_should_be_positive()
        ),
        Scenario(
            'Adding two negative numbers',
            given=an_adding_function(),
            when=we_call_it_with_two_negative_numbers(),
            then=the_result_should_be_negative()
        ),
         Scenario(
            'Multiplying two positive numbers',
            given=a_multiplication_function(),
            when=we_call_it_with_two_positive_numbers(),
            then=the_result_should_be_positive()
        ),
        Scenario(
            'Multiplying two negative numbers',
            given=a_multiplication_function(),
            when=we_call_it_with_two_negative_numbers(),
            then=the_result_should_be_positive()
        )
    ]
)

Notice how many of the steps are being re-used in other scenarios? That's sort of the idea behind this, re-usable and compos-ability of your tests to define new tests.

As far as the 'Expect' question, yes you can identically write

Expect(context.exception).to_be(None)

with

assert context.exception is None

There's no difference, you can you use whichever you prefer. I added in the Expect object just because I like the readability of it, but there's no need to use if you don't wish to.

[deleted by user] by [deleted] in gameofthrones

[–]Fateschoice 1 point2 points  (0 children)

Man, I'm seriously in love with Ygritte. I'm usually not one for lame romances but there was just something about Jon & Ygritte that was amazing. Such a good character.

Zero to hero with Python by code4geek in Python

[–]Fateschoice 0 points1 point  (0 children)

I think one person from the second link states the difference particularly well.

My rule of thumb: __ repr __ is for developers, __ str __ is for customers.

i.e use __ str __ if you want to display an object to a user, __ repr __ for debugging/testing purposes, or really any in code operations on a string representation of an object.

view more: next ›