|
Notorious b.s.d. posted:idgi well ur certainly big!
|
# ? Apr 8, 2018 08:48 |
|
|
# ? Jun 4, 2024 11:04 |
|
i've never used maven, how complicated is writing a custom plugin for it?
|
# ? Apr 9, 2018 05:38 |
|
raminasi posted:i've never used maven, how complicated is writing a custom plugin for it? writing the plugin is very, very simple if you already understand the user side of maven in detail if you have no idea what maven is for, what problems it solves, or how your existing project builds work, plugin authorship might be something of a challenge
|
# ? Apr 9, 2018 06:01 |
|
Gazpacho posted:tweaked slightly to center the face in the frame ok so i am still missing the point, on several levels
|
# ? Apr 9, 2018 06:02 |
|
many of your posts have a weird authoritarian/matter-of-fact vibe, maybe that's why
|
# ? Apr 9, 2018 08:32 |
|
Fiedler posted:Note that project-specific code is totally supported by msbuild. Msbuild lol. That's a good one.
|
# ? Apr 9, 2018 16:56 |
|
Msbuild is inarguably the best build system ever.* *that was produced by Microsoft and is XML based.
|
# ? Apr 9, 2018 18:00 |
|
I don't know about C#, but I have literally never needed to touch msbuild with C++ and have never wanted to. If you're not using cmake and an appropriate binary artifact manager, just lol.
|
# ? Apr 9, 2018 18:15 |
RHEL is deprecating python 2 in their new release
|
|
# ? Apr 10, 2018 21:32 |
|
hell its about time
|
# ? Apr 10, 2018 21:49 |
|
Boiled Water posted:hell its about time https://www.youtube.com/watch?v=Amy_RWpU8t4
|
# ? Apr 10, 2018 22:55 |
|
python 3 is older than python 2 was when 3.0 came out where’s python 4 :v
|
# ? Apr 11, 2018 03:56 |
|
tinaun posted:python 3 is older than python 2 was when 3.0 came out they've learned their lesson
|
# ? Apr 11, 2018 04:01 |
|
VikingofRock posted:RHEL is deprecating python 2 in their new release Good.
|
# ? Apr 11, 2018 04:22 |
|
Gonna lol when everyone's nodejs bindings spontaneously stop building because of its retarded requirement on python 2.7 and no higher.
|
# ? Apr 11, 2018 04:24 |
|
HappyHippo posted:they've learned their lesson Python 2.7's API remaining effectively unchanged for a decade did it more good than any of the new python 3 features. Need to lock 3.7 and start working on a 4.0 they never plan to release.
|
# ? Apr 11, 2018 07:41 |
|
TimWinter posted:Python 2.7's API remaining effectively unchanged for a decade did it more good than any of the new python 3 features. Need to stop making the language loving irrelevant with every x.0 release
|
# ? Apr 11, 2018 07:50 |
|
One thing that C++ has on these dumb P langs- it's forward compatible
|
# ? Apr 11, 2018 07:52 |
|
qhat posted:One thing that C++ has on these dumb P langs- it's forward compatible everything has that on python perl tried for something similar, but both new and old fell into irrelevance before it could really take damage from that
|
# ? Apr 11, 2018 08:03 |
|
Cybernetic Vermin posted:everything has that on python IMO Perl is underrated. I still love the fact that regex support is the most amazing I've ever seen in one language, but it's a pity that's the only good thing about it
|
# ? Apr 11, 2018 08:11 |
|
qhat posted:One thing that C++ has on these dumb P langs- it's forward compatible are you sure about that?
|
# ? Apr 11, 2018 09:05 |
|
qhat posted:One thing that C++ has on these dumb P langs- it's forward compatible still not worth it like, at all
|
# ? Apr 11, 2018 13:07 |
|
qhat posted:Gonna lol when everyone's nodejs bindings spontaneously stop building because of its retarded requirement on python 2.7 and no higher. i'm the scripting language with multiple build systems more complicated than most tax codes
|
# ? Apr 11, 2018 18:04 |
So I'm a little confused by this discussion. Do python minor versions introduce breaking changes?
|
|
# ? Apr 11, 2018 21:47 |
|
VikingofRock posted:So I'm a little confused by this discussion. Do python minor versions introduce breaking changes? Depends on what you consider a breaking change https://blogs.msdn.microsoft.com/ericlippert/2012/01/09/every-public-change-is-a-breaking-change/
|
# ? Apr 11, 2018 21:50 |
|
I don't have enough Python code to run into true breaking changes in minor versions, but every time I make a minor/patch release with changes to internal implementation, I wonder how many issues will get opened because someone depended on some implementation detail. I am at the point where I am considering a semi-malicious (e.g. randomly shuffling returned values if there are no ordering guarantees) implementation of things, to prevent people from depending on implementation details
|
# ? Apr 11, 2018 22:30 |
|
VikingofRock posted:So I'm a little confused by this discussion. Do python minor versions introduce breaking changes? they are about to break the type attributes iirc by making them strings, but that is all 'experimental' if you will (also some asyncio stuff is still changing)
|
# ? Apr 11, 2018 22:42 |
|
Xarn posted:I don't have enough Python code to run into true breaking changes in minor versions, but every time I make a minor/patch release with changes to internal implementation, I wonder how many issues will get opened because someone depended on some implementation detail. golang did this and people complained it wasn't random enough
|
# ? Apr 11, 2018 23:06 |
|
dicts preserve insert order in 3.6 and officially in 3.7
|
# ? Apr 11, 2018 23:06 |
|
Sweeper posted:they are about to break the type attributes iirc by making them strings, but that is all 'experimental' if you will (also some asyncio stuff is still changing) what's this about breaking type attributes?
|
# ? Apr 11, 2018 23:19 |
|
tef posted:dicts preserve insert order in 3.6 and officially in 3.7 so collections.ordereddict not needed anymore?
|
# ? Apr 11, 2018 23:32 |
|
Blinkz0rz posted:so collections.ordereddict not needed anymore? depends. if you only care about iteration then they’re the same now, but if you care about equality then they’re different - dict equality is just “do they have the same key/value pairs”, ordereddict equality also requires the order to be the same. xPanda posted:what's this about breaking type attributes? in 3.6 they’re parsed and names are resolved at the point of declaration, unless you explicitly make them be strings. in 3.7 (if you add a from __future__ import) they’re always left as strings unless something explicitly asks for them to be parsed. not sure it’s a big deal tbh, as a dev who only uses them because it helps pycharm be useful it doesn’t seem likely to break anything I care about
|
# ? Apr 11, 2018 23:51 |
|
from balls import pee
|
# ? Apr 11, 2018 23:53 |
xPanda posted:what's this about breaking type attributes? I looked this up after it was mentioned. An overview is here and the PEP is here. It's not really a breaking change because you opt-in to the new behavior per-module with an import. So no existing python 3.6 code is affected by this change. In python 3.8+, there will be deprecation warning raised for code not using the import, but again I wouldn't really consider that a breaking change.
|
|
# ? Apr 12, 2018 00:48 |
|
tef posted:golang did this and people complained it wasn't random enough https://github.com/golang/go/issues/5362 "It is an inconvenience for me since my map contains only a few keys and I need a random key." haha nice
|
# ? Apr 12, 2018 05:05 |
|
tef posted:dicts preserve insert order in 3.6 and officially in 3.7 no what the hell that’s as bad as calling dictionaries “hashes,” it winds up implying too much about implementation that people then depend on and can then therefore never change what are these people smoking
|
# ? Apr 12, 2018 05:44 |
|
Even if you put a sentence in the docs saying "the order is not defined," people are going to depend on the specific behavior of the implementation anyway -- most unknowingly.
|
# ? Apr 12, 2018 06:28 |
|
tef posted:golang did this and people complained it wasn't random enough Dylan16807 posted:https://github.com/golang/go/issues/5362
|
# ? Apr 12, 2018 07:12 |
|
iirc development builds of .net randomise things like string.GetHashCode() to stop the framework devs from accidentally relying on implementation details
|
# ? Apr 12, 2018 07:24 |
|
|
# ? Jun 4, 2024 11:04 |
|
python 3 started randomizing PYHASHSEED (which is the seed for the language hash() function that determines object identity and then everything that determines that, e.g. dict ordering and like half the language) on interpreter startup which is kinda similar i guess?
|
# ? Apr 12, 2018 12:56 |