Build task should not depend on instanceCheck
See original GitHub issuegradle-aem-multi / sh gradlew :build
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Why __instancecheck__ is not always called depending on ...
The primary mechanism proposed here is to allow overloading the built-in functions isinstance() and issubclass(). The overloading works as ...
Read more >3. Data model — Python 3.11.1 documentation
This object is accessed through the built-in name NotImplemented . Numeric methods and rich comparison methods should return this value if they do...
Read more >Tasks in Visual Studio Code
You can create user level tasks that are not tied to a specific workspace or folder using the Tasks: Open User Tasks command....
Read more >Using Citation Generators Responsibly - Purdue OWL
Citation generators work with the sources you give them. They can't evaluate whether those sources are good or not. This means that it's...
Read more >[Example code]-Why __instancecheck__ is not always ...
I think that the PEP describing __instancecheck__() is faulty. PEP 3119 says: The primary mechanism proposed here is to allow overloading the built-in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m good with that approach, and I understand the balance. My comment was purely out of confusion: “why is the build taking so long?” and when I let it continue to completion “why did the build fail?” I was able to figure out the problem, thanks to my experience with Gradle (and thanks to a nifty task-tree plugin).
I agree that most people will work online, with an AEM instance running, but sometimes you just want to make a quick Java change, run your build/tests and be done, without the need to spin up an instance (I get these spurts of inspiration late at night, and I don’t want to restart my instances constantly 😁). I’m good with just using the flag you provided, or using my
build -x instanceCheck
, but for the benefit of others, I think it should be more prominently featured in the docs.I only found this flag after coming here to open an issue, almost identical to this.
implemented, to be released in 7.1.0